FS#24070 - [fam] Initscript does not check correctly for a running rpcbind (makes initscript useless)
Attached to Project:
Arch Linux
Opened by Tilman Blumenbach (Tblue) - Tuesday, 03 May 2011, 15:21 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 16 May 2011, 14:49 GMT
Opened by Tilman Blumenbach (Tblue) - Tuesday, 03 May 2011, 15:21 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 16 May 2011, 14:49 GMT
|
Details
Description:
With initscripts having been updated to 2011.04.1-2, it is no longer possible to start fam using its initscript. This is because it requires a running rpcbind -- if rpcbind is not running, the fam initscript tries to start it. This works fine, but the script then checks whether rpcbind has been started correctly and is running by checking the existence of /var/run/daemons/rpcbind. The initscripts update has moved the daemon status files to /run/daemons, making that check always fail. Additional info: * Package version: 2.7.0-14 Steps to reproduce: Try to start fam using /etc/rc.d/fam start or rc start fam. Proposed fix: See attached patch. Use ck_daemon to check if rpcbind is running instead of hardcoding the path to its status file. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Monday, 16 May 2011, 14:49 GMT
Reason for closing: Fixed
Additional comments about closing: fam 2.7.0-15
Monday, 16 May 2011, 14:49 GMT
Reason for closing: Fixed
Additional comments about closing: fam 2.7.0-15
A workaround is to add a symlink /var/run/damons -> /run/daemons.
- if [ ! -f /run/daemons/rpcbind ]; then
+ if [ ! -f /run/rpcbind ]; then