ianhogg@cs.umn.edu (Ian J. Hogg) (02/09/91)
I've got past part of my uucp problems. I've got a SparcStation with
SunOs 4.1.1 and a 386 with SCO SysV on it. Anyways I can get the login script
to work in either direction, but the uucico's don't seem to talk to each other.
Here is the full output from uucico on the Sun:
mchFind called (skunkwr)
list (rmail) num = 1
list (/var/spool/uucppublic) num = 1
list (/var/spool/uucppublic) num = 1
list (rmail) list (rnews) list (lp) num = 3
_Request (TRUE), _Switch (TRUE), _CallBack (FALSE), _MyName (), _Commands rmail
_Commands rnews
_Commands lp
chdir(/var/spool/uucp/skunkwr)
conn(skunkwr)
Retry time set to 10 minutes
Device Type skunkwrk wanted
mlock ttyZ3 succeeded
fixline(6, 9600)
processdev: calling setdevcfg(uucico, skunkwrk)
gdial(direct) called
getto ret 6
expect: ("")
got it
expect: ("")
got it
sendthem (^J^J^J^M)
expect: (ogin:)
^M^J^M^M^JSkunkWrk^M^M^J^M^J^M^J^M^M^J^MWelcome to SCO System V/386^M^J^M^M^M^JSkunkWrk!login:got it
sendthem (nuucp^M)
expect: (word:)
nuucp^M^M^JPassword:got it
sendthem (butthead^M)
imsg >^M^JLast successful login for nuucp: Fri Feb 08 16:41:54 CST 1991 on tty1a^M^JLast unsuccessful login for nuucp: Thu Feb 07 14:56:39 CST 1991 on tty1a^M^JUNIX System V/386 Release 3.2^M^JSkunkWrk^M^JCopyright (C) 1984, 1986, 1987, 1988 AT&T^M^JCopyright (C) 1987, 1988 Microsoft Corp.^M^JAll Rights Reserved^M^JCopyright (C) 1988, 1989, 1990 The Santa Cruz Operation, Inc^M^J^PShere=skunkwr^M^M^JLogin Successful: System=skunkwr
omsg "Srathe -x9"
imsg >SkunkWrk^M^M^J^M^J^MWelcome to SCO System V/386^M^J^M^M^M^JSkunkWrk!login: ^PSrathe -x9LOGIN FAILED - failed
exit code 101
Conversation Complete: Status FAILED
TM_cnt: 0
Anyone have any idea what's going on here?
--
===============================================================================
Ian Hogg ianhogg@cs.umn.edu
(612) 225-1401dberg@informix.com (David I. Berg) (02/10/91)
In article <1991Feb8.231342.23814@cs.umn.edu> ianhogg@cs.umn.edu (Ian J. Hogg) writes: >I've got past part of my uucp problems. I've got a SparcStation with >..... >Here is the full output from uucico on the Sun: >..... >expect: (word:) > nuucp^M^M^JPassword:got it >sendthem (butthead^M) >imsg >^M^JLast successful login for nuucp: Fri Feb 08 16:41:54 CST 1991 on tty1a^M^JLast unsuccessful login for nuucp: Thu Feb 07 14:56:39 CST 1991 on tty1a^M^JUNIX System V/386 Release 3.2^M^JSkunkWrk^M^JCopyright (C) 1984, 1986, 1987, 1988 AT&T^M^JCop >yright (C) 1987, 1988 Microsoft Corp.^M^JAll Rights Reserved^M^JCopyright (C) 1988, 1989, 1990 The Santa Cruz Operation, Inc^M^J^PShere=skunkwr^M^M^JLogin Successful: System=skunkwr >omsg "Srathe -x9" >imsg >SkunkWrk^M^M^J^M^J^MWelcome to SCO System V/386^M^J^M^M^M^JSkunkWrk!login: ^PSrathe -x9LOGIN FAILED - failed >exit code 101 >Conversation Complete: Status FAILED > >Anyone have any idea what's going on here? I recall from the backroads of my mind that there is a limit to how much in the way of login messages uucico will tolerate before surrendering. There was message traffic a few months ago about how to preclude a user (ie. uucp) from receiving login messages, but, alas, I didn't keep it. If this is, indeed, why uucico is failing, perhaps another netter will have kept that material. ___ ___ dberg@cougar.informix.com / ) __ . __/ /_ ) _ __ Informix Software Inc. (303) 850-0210 _/__/ (_(_ (/ / (_(_ _/__> (-' -/~ (_- 5299 DTC Blvd #740; Englewood CO 80111 {uunet|pyramid}!infmx!dberg The opinions expressed herein are mine alone.
jmason@gpu.utcs.utoronto.ca (Jamie Mason) (02/10/91)
In article <1991Feb8.231342.23814@cs.umn.edu> ianhogg@cs.umn.edu (Ian J. Hogg) writes: >I've got past part of my uucp problems. I've got a SparcStation with [ Stuff deleted ] >Here is the full output from uucico on the Sun: [ Stuff deleted ] In article <1991Feb9.222138.6831@informix.com> dberg@informix.com (David I. Berg) writes: >I recall from the backroads of my mind that there is a limit to how much in >the way of login messages uucico will tolerate before surrendering. There >was message traffic a few months ago about how to preclude a user (ie. >uucp) from receiving login messages, but, alas, I didn't keep it. If >this is, indeed, why uucico is failing, perhaps another netter will have >kept that material. I do not know if this is system dependant or not, but on the SunOS machines which I use, LOGIN(1) will refrain from printing the message of the day, the check for mail, and the time of the last login, if there is a file called ".hushlogin" in the user's home directory. I use it in one of my accounts where the "message of the day" does not change for weeks, and is long and gets on my nerves. I then have my .login do the mail check, display the time of last login, and show the MOTD itself... But my .login only displays it if it has changed since I last read it. This way I only have to endure each MOTD once. Jamie ... "Who was that Masked Interrupt?" Written On Saturday, February 9, 1991 at 11:34:45pm EST
cliff@demon.co.uk (Cliff Stanford) (02/11/91)
In article <1991Feb8.231342.23814@cs.umn.edu> ianhogg@cs.umn.edu (Ian J. Hogg) writes: >imsg >SkunkWrk^M^M^J^M^J^MWelcome to SCO System V/386^M^J^M^M^M^JSkunkWrk!login: ^PSrathe -x9LOGIN FAILED - failed >exit code 101 >Conversation Complete: Status FAILED > >Anyone have any idea what's going on here? Usually this seems to be that either the terminal or the user account has got locked (SCO Security). Get the sysadmin on the SCO box to check these out. Regards, Cliff. -- Cliff Stanford Email: cliff@demon.co.uk (Work) Demon Systems Limited cms@demon.co.uk (Home) 42 Hendon Lane Phone: 081-349 0063 (Office) London N3 1TT England 0860 375870 (Mobile)
clewis@ferret.ocunix.on.ca (Chris Lewis) (02/13/91)
In article <1991Feb10.184933.17047@demon.co.uk> cliff@demon.co.uk (Cliff Stanford) writes: >In article <1991Feb8.231342.23814@cs.umn.edu> ianhogg@cs.umn.edu (Ian J. Hogg) writes: >>imsg >SkunkWrk^M^M^J^M^J^MWelcome to SCO System V/386^M^J^M^M^M^JSkunkWrk!login: ^PSrathe -x9LOGIN FAILED - failed >>exit code 101 >>Conversation Complete: Status FAILED >>Anyone have any idea what's going on here? > Usually this seems to be that either the terminal or the user account >has got locked (SCO Security). Get the sysadmin on the SCO box to check >these out. Possible. But the rest of the log seems to indicate that Ian's machine *did* manage to log in: the Shere=skunkwr came from the SCO systems's uucico, and Ian's machine did seem to respond with "Hi, I'm so-and-so" (S<I disremember - not in this excerpt> -x9). SCO security wouldn't have let him in that far. Neither would a bum password. Other's have suggested skunkwr's motd and other gunge was too long. Yes, HDB will sometimes say "Enough already" and drop the line. But again, this would not have had the "S<Ian's machine> -x9" line either. It's more suggestive that the SCO system said, after Ian's machine told it who it was, "I don't know who you are, go AWAY!". Eg: Ian's machine isn't in the SCO's Permissions/Systems/L.sys/USERFILE or whatever. An examination of skunkwr's logs (particularly the stuff under ".Admin" if it's HDB) will probably show this. Many versions of uucico will place a "You are unknown to me" into the logs, on both sides of the attempted connection, or sometimes in the uustat -m output. Good luck. -- Chris Lewis, Phone: (613) 832-0541, Internet: clewis@ferret.ocunix.on.ca UUCP: uunet!mitel!cunews!latour!ecicrl!clewis; Ferret Mailing List: (ferret-request@eci386); Psroff (not Adobe Transcript) enquiries: psroff-request@eci386, current patchlevel is *7*.