mgetty's controled my modem

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

>>>>> "Chi" == Chi Cheng <simon@guomai.sh.cn> writes:

    Chi> Dear friends: I have just read mgetty.info and add a line in
    Chi> /etc/inittab S1:23:respawn:/sbin/mgetty -x 3 -n 5 -s 38400
    Chi> ttyS1 but then, I am unable to access my modem after reboot,
    Chi> based on its info, mgetty could go away while other programme
    Chi> want use my modem. But i failed to use "cu -l /dev/modem" as
    Chi> usual and unable to use chat and pppd to dial out. Is there
    Chi> any idea to solve this problem? 

rm /dev/modem

Don't use /dev/modem, since your inittab has mgetty hooked to
/dev/ttyS1.  The reason for this is that the lock file is based on the 
device name, and /dev/ttyS1 is not the same name as /dev/modem.  Since 
/dev/modem is a symlink, get rid of it.  This is a good idea anyway:
think about a system with more than one modem.  What would /dev/modem
mean in a situation like this.  The avoidance of /dev/modem is clearly 
spelled out in the docs and the FAQ, and has been asked about hundreds 
of times before on this list.  Check the archives at
http://www.elilabs.com/mgarc/index.html for the history of this
problem. 

-- 
--------  "And there came a writing to him from Elijah"  [2Ch 21:12]  --------
R. J. Brown III  rj@elilabs.com http://www.elilabs.com/~rj  voice 847 543-4060
Elijah Laboratories Inc. 457 Signal Lane, Grayslake IL 60030  fax 847 543-4061
-----  M o d e l i n g   t h e   M e t h o d s   o f   t h e   M i n d  ------