Re: [hylafax-users] "Can not lock modem device" every 30 secs

[frbn <frbn@xxxxxxxxxxxx>]

Joerg Beyer wrote:

> Giulio Orsero schrieb:
>
> > On 4/30/05, Joerg Beyer <Joerg.Beyer@xxxxxx> wrote:
> >
> > > Apr 30 19:34:04 server FaxGetty[1333] MODEM USR USRobotics [...]
> > > Apr 30 19:34:38 server FaxGetty[1392] ANSWER: Can not lock modem device
> > > Apr 30 19:34:38 server FaxGetty[1392] MODEM USR USRobotics [...]
> > > Apr 30 19:34:42 server FaxGetty[1333] ANSWER: Can not lock modem device
> > > 1333 ?  S       0:00    /usr/sbin/faxgetty ttyS1
> > > [...]
> > > 1392 ?  Ss      0:00    /usr/sbin/faxgetty /dev/ttyS1
> >
> >
> >
> > > I have my faxgetty started in "inittab":
> > > T1:23:respawn:/usr/sbin/faxgetty /dev/ttyS1
> >
> >
> >
> > So, why not starting from using ttyS1 in place of /dev/ttyS1 in inittab?
> > Them kill all faxgettys and see what happens.
>
>
> Did change the setting in inittab, but didn't help anything. Nothing's 
> changed.

Did you run "telinit q" to respawn init ?

> > You can use ps axl to see the Parent PID for faxgetty and see who 
> > started what.
I use "ps fax" ;)

> The parent process is init that starts both "faxgetty"s.
>
> Is it correct that there are two faxgetty processes running all the time?

One faxgetty for each modem.

   regards
franck

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*