![]() |
Instead of there being a tty<##>.conf in /etc/init for each tty to start the faxgetty at boot, they should be in /etc/event.d For example, the contents of /etc/init.d/ttyR0.conf was as follows:- # ttyR0 - faxgetty # # This service maintains a faxgetty on ttyR0 from the point the system is # started until it is shut down again. start on stopped rc RUNLEVEL=[2345] stop on runlevel [!2345] respawn exec /usr/sbin/faxgetty ttyR0 # # The corresponding new entry I have in /etc/event.d/ttyR0 is :- # ttyR0 - faxgetty # # This service maintains a faxgetty on ttyR0 from the point the system is # started until it is shut down again. start on runlevel 2 start on runlevel 3 start on runlevel 4 start on runlevel 5 stop on runlevel 0 stop on runlevel 1 stop on runlevel 6 respawn exec /usr/sbin/faxgetty ttyR0 # # Which I believe is functionally identical to the first. Obviously this is repeated for each tty you need a faxgetty on. -----Original Message----- From: Giuseppe Sacco [mailto:giuseppe@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, May 11, 2010 4:25 AM To: James Smith Cc: hylafax-users Subject: Re: [hylafax-users] Problems after upgrade to 10.04 Il giorno lun, 10/05/2010 alle 07.59 -0400, James Smith ha scritto: > I did the upgrade and it went mostly ok > > The only thing that was different was the handling of the faxgettys > > I found you had to create entries in /etc/event.d/ instead of init.d > as they have deprecated init.d completely now Would you like to share these entries, I could add them to next Debian (and Ubuntu) packages. Bye, Giuseppe ____________________ 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*