Bug 6528

Summary:	faxgetty will not start from inittab
Product:	Mageia	Reporter:	james Whitby <jim>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	balcaen.john, ennael1, fundawang, mageia, stormi-mageia
Version:	2	Keywords:	PATCH, Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	hylafax-client-5.5.0-3.mga2.src.rpm	CVE:
Status comment:
Attachments:	faxgetty for hylafax using systemd faxq daemon for hylafax and systemd

Description james Whitby 2012-06-21 01:05:59 CEST

Description of problem:
Appears that hylafax( et all ) has not been converted to use systemd.
Faxgetty is ignored in inittab.

telinit Q returns ok but no faxgetty process is running.

chkconfig --add hylafax-server appears to function, but
chkconfig --list hylafax-server shows proper info
service hylafax-server start gives unknown process



Version-Release number of selected component (if applicable):


How reproducible:

install hylafax server client
 run faxsetup
be sure to run faxaddmodem.

edit inittab, uncomment faxgetty line, add runlevel 5, telinit Q.

service hylafax-server start


Steps to Reproduce:
1.
2.
3.

I see in another bug that there isn't a maintainer for hylafax.

I do not know anything about systemd, but if someone can point me in the right direction, I'll try to make things work. 

I need this to replace a very old ( P4 ) machine in a warehouse. So whatever I can do I will.

Thanks.

Comment 1 Manuel Hiebel 2012-06-21 19:38:38 CEST

>I do not know anything about systemd, but if someone can point me in the right
>direction, I'll try to make things work. 

https://wiki.mageia.org/en/Features/Systemd, colin ideas maybe ?

CC: (none) => mageia

Comment 2 james Whitby 2012-06-25 23:09:09 CEST

Created attachment 2493 [details]
faxgetty for hylafax using systemd

Comment 3 james Whitby 2012-06-25 23:10:09 CEST

Created attachment 2494 [details]
faxq daemon for hylafax and systemd

Comment 4 james Whitby 2012-06-25 23:11:45 CEST

I have it functioning. Here are my files and info.

I'm sure there are much better ways to accomplish this, but for now this works. 

faxfett@,service is in /lib/systemd/system.
/etc/systemd/system/faxgetty@ttyS0.service is linked to faxgetty@service

hylafax-server.service is in /lib/systemd/system

Comment 5 Colin Guthrie 2012-07-27 16:32:13 CEST

Sorry for the late reply. This seems like a sensible solution overall.

Comment 6 Samuel Verschelde 2013-08-27 18:33:30 CEST

Hi, thanks for reporting this bug and providing a patch.
As there is no maintainer for this package I added the committers in CC.

(Please assign the bug to you and set the status to 'assigned' if you are working on it)

Keywords: (none) => PATCH, Triaged
CC: (none) => balcaen.john, ennael1, fundawang, stormi

Comment 7 Manuel Hiebel 2013-10-22 12:21:08 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 8 Manuel Hiebel 2013-11-23 16:16:37 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD