SOLVED faxgetty fails. rc.local fails to provide path to ttyIAX0 thru 3.

chris_c_

Active Member
Joined
Aug 19, 2010
Messages
509
Reaction score
67
Github issue : https://github.com/EspaceNetworks/IncrediblePBXCentOS7/issues/12

Run rc.local and you get no such file or directory error as bash fails to find faxgetty at /usr/sbin/.

~$ /etc/rc.local
/etc/rc.local: line 17: /usr/sbin/faxgetty: No such file or directory
/etc/rc.local: line 18: /usr/sbin/faxgetty: No such file or directory
/etc/rc.local: line 19: /usr/sbin/faxgetty: No such file or directory
/etc/rc.local: line 20: /usr/sbin/faxgetty: No such file or directory
~$


Lines from rc.local

/usr/sbin/faxgetty -D ttyIAX0
/usr/sbin/faxgetty -D ttyIAX1
/usr/sbin/faxgetty -D ttyIAX2
/usr/sbin/faxgetty -D ttyIAX3


Bug in the installer script.
 
Last edited:

wardmundy

Nerd Uno
Joined
Oct 12, 2007
Messages
15,083
Reaction score
2,601
We do not support the 32-bit implementation of CentOS 7.
 
Last edited:

chris_c_

Active Member
Joined
Aug 19, 2010
Messages
509
Reaction score
67
We do not support the 32-bit implementation of CentOS 7.
Nice graphic.
This bug has nothing to do with 64/32 bit.
The path is wrong, for both 32 and 64 bit.
I've posted a fix.
 

dicko

Still learning but earning
Joined
Oct 30, 2015
Messages
644
Reaction score
234
A bad fix IMHO, always use full path names to binaries in inittab

a better fix

echo "
t$COUNT:23:respawn:$(which faxgetty) ttyIAX$COUNT > /var/log/iaxmodem/iaxmodem.log
" >> /etc/inittab


if faxgetty is not where it normally is (/usr/sbin)
 
Last edited:
  • Like
Reactions: jerrm

chris_c_

Active Member
Joined
Aug 19, 2010
Messages
509
Reaction score
67
A bad fix IMHO, always use full path names to binaries in inittab

a better fix

echo "
t$COUNT:23:respawn:${which faxgetty) ttyIAX$COUNT > /var/log/iaxmodem/iaxmodem.log
" >> /etc/inittab


if faxgetty is not where it normally is (/usr/sbin)
Thanks mate,
Right you are, the path to faxgetty needs to be dynamically determined at the time the incredblefax11 install script runs.
And, you've discovered yet another place in the script with this bug (wrong path on faxgetty).
Since inittab pertains to CentOS 6.
The first line of /etc/inittab reads:
Code:
# inittab is no longer used when using systemd.
So CentOS 7 doesn't use inittab any longer.
Your line adding commands to inittab is a good fix to avoid a bugged incrediblefax11 install on CentOS 6.

I'll fix all of these parts where it's inserting commands into start scripts, so the paths are determined at run time of the script and not hard coded to a preset value, and not missing.
 

chris_c_

Active Member
Joined
Aug 19, 2010
Messages
509
Reaction score
67
@wardmundy mate I think we're duplicating efforts on these bug fixes.
Most of the duplication could be reduced by using the same source code management system.
By far most open source projects use git/github including frepbx, xivo, asterisk and linus' linux kernel.
https://github.com/torvalds/linux (updated 44 minutes ago)
I urge you to check out github and see if you feel right posting the code and fixes on there.
 

Members online

PIAF 5 - Powered by 3CX

Forum statistics

Threads
22,319
Messages
137,021
Members
14,550
Latest member
treimers