Re: /usr/bin/lock is broken in 3.0

1999-03-03 Thread Sheldon Hearn
On Wed, 03 Mar 1999 19:06:25 +0200, Sheldon Hearn wrote: > You're not using PAM, perhaps? I'd greatly appreciate it if everyone would ignore that comment. Thanks, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message

Re: /usr/bin/lock is broken in 3.0

1999-03-03 Thread Chris Costello
On Wed, Mar 3, 1999, Jan B. Koum put this into my mailbox: > Sorry, but I just could not track down the problem myself :( > > With 2.2 box you get: > > shell6: {104} lock -np > lock: /dev/ttyp8 on shell6.ba.best.com. no timeout > time now is Wed Mar 3 08:52:55 PST 1999 > Key: > >

Re: /usr/bin/lock is broken in 3.0

1999-03-03 Thread Sheldon Hearn
On Wed, 03 Mar 1999 08:57:05 PST, "Jan B. Koum " wrote: > nautilus% ls -l /usr/bin/lock > -r-sr-xr-x 1 root wheel 5636 Feb 3 21:06 /usr/bin/lock > nautilus% lock -np > nautilus% > > Can someone tell me what is going on? Works for me. $ uname -a FreeBSD axl.noc.iafrica.com 4.0-CURRE

/usr/bin/lock is broken in 3.0

1999-03-03 Thread Jan B. Koum
Sorry, but I just could not track down the problem myself :( With 2.2 box you get: shell6: {104} lock -np lock: /dev/ttyp8 on shell6.ba.best.com. no timeout time now is Wed Mar 3 08:52:55 PST 1999 Key: And on 3.x/4.x you get: nautilus% ls -l /usr/bin/lock -r-sr-xr-x 1