Hello,

is there a solution at hand for the dreaded mgetty-problem on
FreeBSD 6.0-STABLE? I couldn't find anything on the net except
that some people have the same problem, and that PR i386/87208
contains some interesting insight.

It is ok for me to 'kill -HUP 1' to get mgetty running (see
below), but this does not seem to be a good solution really :-(

Apart from that, 6.0 looks quite good! Thanx!

Regards,
Holger Kipp

PS: Any ideas how to get rid of the 
    "cannot open /proc/<pid>/cmdline"-Message?
    Looks like linuxism to me...

----------------------

11/14 14:18:10 ad0  mgetty: interim release 1.1.33-Apr10
11/14 14:18:10 ad0  check for lockfiles
11/14 14:18:10 ad0  locking the line
11/14 14:18:11 ad0  mod: cannot make /dev/cuad0 stdin: Bad file descriptor
11/14 14:18:11 ad0  open device /dev/cuad0 failed: Bad file descriptor
11/14 14:18:11 ad0  cannot get terminal line dev=cuad0, exiting: Bad file 
descriptor
--
11/14 14:18:11 ad0  mgetty: interim release 1.1.33-Apr10
11/14 14:18:11 ad0  check for lockfiles
11/14 14:18:11 ad0  locking the line
11/14 14:18:11 ad0  lowering DTR to reset Modem
11/14 14:18:12 ad0  send: ATS0=0Q0&D3&C1[0d]
11/14 14:18:12 ad0  waiting for ``OK'' ** found **
11/14 14:18:12 ad0  waiting...
11/14 14:18:53 ad0  lock not made: lock file exists (pid=784)
11/14 14:18:53 ad0  cannot open /proc/784/cmdline: No such file or directory
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to