[opensuse] inittab Faxgetty
I have upgraded my Hylafax server to 12.1. Installed Hylafax works fine. But i can't get the faxgetty to work in the /etc/inittab file. I have tried : mo:2345:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 and even: mo:35:respawn:/usr/lib/fax/faxgetty ttyS0 mo:2345:respawn:/usr/lib/fax/faxgetty ttyS0 modem will not respawn after after reboot. If i run: usr/lib/faxgetty -D ttyS0 Modem works fine until I reboot. Then I tried: I created a file /etc/systemd/system/faxgetty-ttyS0.service [Unit] Description=HylaFAX faxgetty for ttyS0 [Service] User=root Group=root Restart=always RestartSec=30 ExecStart=/usr/lib/fax/faxgetty /dev/ttyS0 [Install] WantedBy=multi-user.target Then in terminal I issued 'systemctl start faxgetty-ttyS0.service' Modem starts respawns great. Reboot and modem still dead. Any help would very appreciated. Steven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/3/2012 9:07 PM, Steven wrote:
I have upgraded my Hylafax server to 12.1. Installed Hylafax works fine. But i can't get the faxgetty to work in the /etc/inittab file. I have tried : mo:2345:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 and even: mo:35:respawn:/usr/lib/fax/faxgetty ttyS0 mo:2345:respawn:/usr/lib/fax/faxgetty ttyS0 modem will not respawn after after reboot.
If i run: usr/lib/faxgetty -D ttyS0 Modem works fine until I reboot.
Then I tried:
I created a file /etc/systemd/system/faxgetty-ttyS0.service
[Unit] Description=HylaFAX faxgetty for ttyS0
[Service] User=root Group=root Restart=always RestartSec=30 ExecStart=/usr/lib/fax/faxgetty /dev/ttyS0
[Install] WantedBy=multi-user.target
Then in terminal I issued 'systemctl start faxgetty-ttyS0.service' Modem starts respawns great. Reboot and modem still dead.
Any help would very appreciated.
Steven I had problems with systemd and hylafax (amongst many others). I went back to SysVInit and Hylafax is working great with mo:35:respawn:/usr/sbin/faxgetty /dev/ttyS0 in /etc/inittab IMHO, systemd is quite fully cooked yet.
-- --Moby ty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
How do put back to SysVInit permanent? I know about the press F5 and select systemv. The change is only for that boot. Will swiching to SysVInit affect anything else? On 04/03/2012 09:33 PM, Moby wrote:
On 4/3/2012 9:07 PM, Steven wrote:
I have upgraded my Hylafax server to 12.1. Installed Hylafax works fine. But i can't get the faxgetty to work in the /etc/inittab file. I have tried : mo:2345:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 and even: mo:35:respawn:/usr/lib/fax/faxgetty ttyS0 mo:2345:respawn:/usr/lib/fax/faxgetty ttyS0 modem will not respawn after after reboot.
If i run: usr/lib/faxgetty -D ttyS0 Modem works fine until I reboot.
Then I tried:
I created a file /etc/systemd/system/faxgetty-ttyS0.service
[Unit] Description=HylaFAX faxgetty for ttyS0
[Service] User=root Group=root Restart=always RestartSec=30 ExecStart=/usr/lib/fax/faxgetty /dev/ttyS0
[Install] WantedBy=multi-user.target
Then in terminal I issued 'systemctl start faxgetty-ttyS0.service' Modem starts respawns great. Reboot and modem still dead.
Any help would very appreciated.
Steven I had problems with systemd and hylafax (amongst many others). I went back to SysVInit and Hylafax is working great with mo:35:respawn:/usr/sbin/faxgetty /dev/ttyS0 in /etc/inittab IMHO, systemd is quite fully cooked yet.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/3/2012 9:41 PM, Steven wrote:
How do put back to SysVInit permanent? I know about the press F5 and select systemv. The change is only for that boot. Will swiching to SysVInit affect anything else?
On 04/03/2012 09:33 PM, Moby wrote:
On 4/3/2012 9:07 PM, Steven wrote:
I have upgraded my Hylafax server to 12.1. Installed Hylafax works fine. But i can't get the faxgetty to work in the /etc/inittab file. I have tried : mo:2345:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 and even: mo:35:respawn:/usr/lib/fax/faxgetty ttyS0 mo:2345:respawn:/usr/lib/fax/faxgetty ttyS0 modem will not respawn after after reboot.
If i run: usr/lib/faxgetty -D ttyS0 Modem works fine until I reboot.
Then I tried:
I created a file /etc/systemd/system/faxgetty-ttyS0.service
[Unit] Description=HylaFAX faxgetty for ttyS0
[Service] User=root Group=root Restart=always RestartSec=30 ExecStart=/usr/lib/fax/faxgetty /dev/ttyS0
[Install] WantedBy=multi-user.target
Then in terminal I issued 'systemctl start faxgetty-ttyS0.service' Modem starts respawns great. Reboot and modem still dead.
Any help would very appreciated.
Steven I had problems with systemd and hylafax (amongst many others). I went back to SysVInit and Hylafax is working great with mo:35:respawn:/usr/sbin/faxgetty /dev/ttyS0 in /etc/inittab IMHO, systemd is quite fully cooked yet.
I just installed the sysvinit rpm via zypper - that took care of removing systemd and no ill effects at all -- --Moby -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks I'll try it tomorrow.. On 04/03/2012 09:54 PM, Moby wrote:
On 4/3/2012 9:41 PM, Steven wrote:
How do put back to SysVInit permanent? I know about the press F5 and select systemv. The change is only for that boot. Will swiching to SysVInit affect anything else?
On 04/03/2012 09:33 PM, Moby wrote:
On 4/3/2012 9:07 PM, Steven wrote:
I have upgraded my Hylafax server to 12.1. Installed Hylafax works fine. But i can't get the faxgetty to work in the /etc/inittab file. I have tried : mo:2345:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 mo:35:respawn:/usr/lib/fax/faxgetty /dev/ttyS0 and even: mo:35:respawn:/usr/lib/fax/faxgetty ttyS0 mo:2345:respawn:/usr/lib/fax/faxgetty ttyS0 modem will not respawn after after reboot.
If i run: usr/lib/faxgetty -D ttyS0 Modem works fine until I reboot.
Then I tried:
I created a file /etc/systemd/system/faxgetty-ttyS0.service
[Unit] Description=HylaFAX faxgetty for ttyS0
[Service] User=root Group=root Restart=always RestartSec=30 ExecStart=/usr/lib/fax/faxgetty /dev/ttyS0
[Install] WantedBy=multi-user.target
Then in terminal I issued 'systemctl start faxgetty-ttyS0.service' Modem starts respawns great. Reboot and modem still dead.
Any help would very appreciated.
Steven I had problems with systemd and hylafax (amongst many others). I went back to SysVInit and Hylafax is working great with mo:35:respawn:/usr/sbin/faxgetty /dev/ttyS0 in /etc/inittab IMHO, systemd is quite fully cooked yet.
I just installed the sysvinit rpm via zypper - that took care of removing systemd and no ill effects at all
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-04 04:41, Steven wrote:
How do put back to SysVInit permanent? I know about the press F5 and select systemv. The change is only for that boot.
There are two methods. One is published in the 12.1 release notes that you should read. Another is, once you booted wit the F5 trick, look at what line the kernel got (in the messages log), and modify one item in the menu.lst file, or add a new entry.
Will swiching to SysVInit affect anything else?
It might. If not now, in the future. Somebody here should know how to adapt hylafax to systemd. You already wrote a service file, adding it to the system should be easy. Wait a bit. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk98HzgACgkQIvFNjefEBxpLEgCfezMsUSSNoVrdOMZFuc46Db6/ GNAAn2ncegMqz/7H1GcDnNk3/EvlmK2v =VmY0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks, I will wait to see if someone can adapt hylafax(faxgetty) to systemd. i do not not need any future hiccups. It is a working server nfs, egroupware, openfire just to name a few. This is my server for my and my wife's business. Steven On 04/04/2012 05:15 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
How do put back to SysVInit permanent? I know about the press F5 and select systemv. The change is only for that boot. There are two methods. One is published in the 12.1 release notes that you should read. Another is, once you booted wit the F5 trick, look at what
On 2012-04-04 04:41, Steven wrote: line the kernel got (in the messages log), and modify one item in the menu.lst file, or add a new entry.
Will swiching to SysVInit affect anything else? It might. If not now, in the future.
Somebody here should know how to adapt hylafax to systemd. You already wrote a service file, adding it to the system should be easy. Wait a bit.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk98HzgACgkQIvFNjefEBxpLEgCfezMsUSSNoVrdOMZFuc46Db6/ GNAAn2ncegMqz/7H1GcDnNk3/EvlmK2v =VmY0 -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
As a guy who packages and maintains Hylafax+ for suse, https://build.opensuse.org/package/show?package=HylaFAX%2B&project=home%3Aaljex (look at all those lovely green build success...) I can tell you I don't know when if ever I'll get around to adding systemd support. If someone else does it I'll probably include it, but still I'll probably never test it first hand so won't be able to ensure it actually works right. I DO use and test the package, but in sysv init systems. Also, such fax server systems often need proprietary 3rd party init scripts for special hardware for T1/isdn/t.38/serial hardware. These are universally sysv init scripts that have to work on solaris and hpux and unixware and open server and freebsd etc etc etc as well as linux. Often they are also long since abandoned and no longer updated by the manufacturers, or the manufacturers no longer even exist. The hardware still works and the serial and telephony standards haven't changed to make the hardware obsolete, and copies of the last official software support downloads exist and still work, but it's not legal for anyone to update them to systemd and repackage and redistribute them even if someone wanted to. You'd have to develop a download-and-modify script and distribute that for each individual thing. Multiply that times 40 zillion other software and yet systemd pushers are not guilty of screwing things up.... -- bkw On 4/4/2012 9:11 AM, Steven wrote:
Thanks, I will wait to see if someone can adapt hylafax(faxgetty) to systemd. i do not not need any future hiccups. It is a working server nfs, egroupware, openfire just to name a few. This is my server for my and my wife's business. Steven
On 04/04/2012 05:15 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
How do put back to SysVInit permanent? I know about the press F5 and select systemv. The change is only for that boot. There are two methods. One is published in the 12.1 release notes that you should read. Another is, once you booted wit the F5 trick, look at what
On 2012-04-04 04:41, Steven wrote: line the kernel got (in the messages log), and modify one item in the menu.lst file, or add a new entry.
Will swiching to SysVInit affect anything else? It might. If not now, in the future.
Somebody here should know how to adapt hylafax to systemd. You already wrote a service file, adding it to the system should be easy. Wait a bit.
- -- Cheers / Saludos,
Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk98HzgACgkQIvFNjefEBxpLEgCfezMsUSSNoVrdOMZFuc46Db6/ GNAAn2ncegMqz/7H1GcDnNk3/EvlmK2v =VmY0 -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Figured out a simple cheat fix: I created a file /etc/systemd/system/faxgetty.service [Unit] Description=FaxGetty Start Modem ttyS0 After=getty.target [Service] Type=simple User=root Group=root Restart=always ExecStart=/usr/lib/fax/faxgetty /dev/ttyS0 TimeoutSec=0 [Install] WantedBy=multi-user.target Then I setup a cron job at boot it runs systemctl start faxgetty.service Works perfect On 04/04/2012 04:08 PM, Brian K. White wrote:
As a guy who packages and maintains Hylafax+ for suse, https://build.opensuse.org/package/show?package=HylaFAX%2B&project=home%3Aaljex
(look at all those lovely green build success...)
I can tell you I don't know when if ever I'll get around to adding systemd support. If someone else does it I'll probably include it, but still I'll probably never test it first hand so won't be able to ensure it actually works right. I DO use and test the package, but in sysv init systems. Also, such fax server systems often need proprietary 3rd party init scripts for special hardware for T1/isdn/t.38/serial hardware. These are universally sysv init scripts that have to work on solaris and hpux and unixware and open server and freebsd etc etc etc as well as linux. Often they are also long since abandoned and no longer updated by the manufacturers, or the manufacturers no longer even exist. The hardware still works and the serial and telephony standards haven't changed to make the hardware obsolete, and copies of the last official software support downloads exist and still work, but it's not legal for anyone to update them to systemd and repackage and redistribute them even if someone wanted to. You'd have to develop a download-and-modify script and distribute that for each individual thing.
Multiply that times 40 zillion other software and yet systemd pushers are not guilty of screwing things up....
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-04-06 05:15, Steven wrote:
Then I setup a cron job at boot it runs systemctl start faxgetty.service
Works perfect
Interesting trick! :-) - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk9+YSkACgkQIvFNjefEBxondACgyh4gpf62hcy3JDJW8LeJGQyZ QWsAoI7U9Olg7ShBYXdWBLXbI3erKhJs =T4bx -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2012-04-05 at 22:15 -0500, Steven wrote:
Figured out a simple cheat fix:
I created a file /etc/systemd/system/faxgetty.service
You might find this thread of interest, the problem is similar: http://forums.opensuse.org/showthread.php?t=475468 - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk+9OSIACgkQtTMYHG2NR9XMyACeL/L/0nFlXqfKkwCEh7hUD/ap MwoAn1lxdvt0qA0KgNXauhofgBan4bz2 =nIaJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On Thursday, 2012-04-05 at 22:15 -0500, Steven wrote:
Figured out a simple cheat fix:
I created a file /etc/systemd/system/faxgetty.service
You might find this thread of interest, the problem is similar:
Bit of long thread, just scroll all the way down to see the solution. -- Per Jessen, Zürich (16.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 5/23/2012 3:23 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2012-04-05 at 22:15 -0500, Steven wrote:
Figured out a simple cheat fix:
I created a file /etc/systemd/system/faxgetty.service
You might find this thread of interest, the problem is similar:
Haha I love that. Wonderful systemd... so much better. So worth the disruption... Poettering you are our hero and savior! ----quote---- I mean its a long way from 2:2345:respawn:/sbin/mingetty tty2 to [Unit] Description=Getty on %I BindTo=dev-%i.device After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service # If additional gettys are spawned during boot then we should make # sure that this is synchronized before getty.target, even though # getty.target didn't actually pull it in. Before=getty.target [Service] Environment=TERM=linux ExecStart=-/sbin/agetty %I 38400 Restart=always RestartSec=0 UtmpIdentifier=%I TTYPath=/dev/%I TTYReset=yes TTYVHangup=yes TTYVTDisallocate=yes KillMode=process # Unset locale for the console getty since the console has problems # displaying some internationalized messages. Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= LC_MEASUREMENT= LC_IDENTIFICATION= # Some login implementations ignore SIGTERM, so we send SIGHUP # instead, to ensure that login terminates cleanly. KillSignal=SIGHUP [Install] Alias=getty.target.wants/getty@tty1.service ----quote---- -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Brian K. White -
Carlos E. R. -
Moby -
Per Jessen -
Steven