![]() |
Hello Darren, I used the hylafax-4.1beta3-1rh6.i386.rpm from ftp.hylafax.org to set up hylafax and it gave me troubles with locking the serial device. During reading HylaFax mailing lists, I noticed that mainly RH6 users have the same problems as I do. Log: lut 26 19:03:10 inet FaxQueuer[29317]: SUBMIT JOB 1 lut 26 19:03:15 inet FaxGetty[29356]: ANSWER: Can not lock modem device lut 26 19:03:20 inet FaxSend[29454]: MODEM MULTI-TECH SYSTEMS MT2834ZDXI/0316A lut 26 19:03:21 inet FaxSend[29454]: SEND FAX: JOB 1 DEST 2660438 COMMID 00000002 lut 26 19:04:27 inet FaxSend[29454]: SEND FAILED: No answer from remote lut 26 19:04:51 inet FaxGetty[29356]: MODEM MULTI-TECH SYSTEMS MT2834ZDXI/0316A lut 26 19:05:16 inet FaxGetty[29356]: ANSWER: Can not lock modem device The cu also has the problem: [root@inet misc]# cu -l ttyS01 cu: creat (/var/lock/TMP0000007364): Brak dost�pu [MK: it reads "no access", I use localized version of Mandrake] cu: ttyS01: Line in use I checked the permissions of the /var/lock itself and they seem fine: drwxrwxr-x 6 root uucp 4096 lut 26 19:36 lock/ There are some strange file ownership rights set on the device that was created during setup of the modem: prw-rw-rw- 1 uucp wheel 0 lut 26 19:00 FIFO.cua1| (I changed permissions manually later but it didn't help after finding mail from some guy from Germany that even though cu isn't suid but strace shows uucp's effective uid later, so I thought that changing permissions for ugo could help such programs access the device, but it didn't help). Minicom seems to have no problem communicating with modem. The modem itself probably isn't a problem since it's on the recommended list for Hylafax. Anybody knows the cause of the problem? Regards, Marcin Krol ...Put knot yore trust inn spel chequers ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null