| Summary: | lock doesn't lock (doesn't work) | ||
|---|---|---|---|
| Product: | Base System | Reporter: | rcharron <rcharron> |
| Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 3.2-RELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
rcharron
1999-08-20 07:00:00 UTC
On Thu, Aug 19, 1999, rcharron@sci-syscom.com wrote: > >Description: > when typing 'lock', just sits there like nothing happened, no matter what flags I give it too. Does this exist in -STABLE? > >How-To-Repeat: > lock <enter> > $_ FreeBSD holly.dyndns.org 4.0-CURRENT FreeBSD 4.0-CURRENT #7: Fri Aug 6 11:57:22 CDT 1999 root@holly.dyndns.org:/usr/src/sys/compile/Holly i386 $ lock Key: Again: lock: /dev/ttyp6 on holly.dyndns.org. timeout in 15 minutes time now is Fri Aug 20 01:16:57 CDT 1999 Key: $ lock -p -n lock: /dev/ttyp6 on holly.dyndns.org. no timeout time now is Fri Aug 20 01:19:03 CDT 1999 Key: $ -- |Chris Costello <chris@calldei.com> |All you need to know is the user interface. - J. Redford `--------------------------------------------------------- On Thu, Aug 19, 1999 at 10:55:27PM -0700, rcharron@sci-syscom.com wrote: > > when typing 'lock', just sits there like nothing happened, no matter what flags I give it too. > >How-To-Repeat: > lock <enter> > $_ > Do you refer to the /usr/bin/lock? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age How long do you leave it before giving up and hitting Ctrl-C? Give it a while. You might find that it's having a problem with gethostname(). Is your machine's hostname configured? What do you see when you do this on the command-line: cat /etc/resolv.conf hostname Ciao, Sheldon. On Fri, Aug 20, 1999, Sheldon Hearn wrote: > How long do you leave it before giving up and hitting Ctrl-C? Give it a > while. You might find that it's having a problem with gethostname(). Is > your machine's hostname configured? What do you see when you do this on > the command-line: There are no network operations in gethostname(3): int gethostname(name, namelen) char *name; int namelen; { int mib[2]; size_t size; mib[0] = CTL_KERN; mib[1] = KERN_HOSTNAME; size = namelen; if (sysctl(mib, 2, name, &size, NULL, 0) == -1) return (-1); return (0); } -- |Chris Costello <chris@calldei.com> |I haven't lost my mind; it's backed up on tape somewhere. `--------------------------------------------------------- On Fri, 20 Aug 1999 04:36:01 EST, Chris Costello wrote:
> > How long do you leave it before giving up and hitting Ctrl-C?
>
> There are no network operations in gethostname(3):
That's a point. ;-)
I'd still like to know how long the originator waited. You think it's
having a problem getting tty parameters? I'd be interested in knowing
whether this was run from the console, an xterm or what.
Ciao,
Sheldon.
State Changed From-To: open->closed Timed out. It is suspected that the originator was not using FreeBSD's stock lock. |