Pandora FMS Community

pid returns garbage in pandora scripts

qus · 17 mar 2009, 4:10 · 2 mensajes · 53 visitas

  1. Inicio del debate

    Hello, Almost all Pandora scripts depend on pid -x command: PANDORA_PID=$(pidof -x $PANDORA_DAEMON if [ ! -z $PANDORA_PID ] then echo "Pandora FMS Data Server is currently running on this machine with PID ($PANDORA_PID). Aborting now..." exit 1 Unfortunately pidof on my Suse and Ubuntu return garbage: Pandora FMS Network Server is currently running on this machine with PID (4741). Aborting now... war133:/etc/init.d # ./pandora_network start Pandora FMS Network Server is currently running on this machine with PID (4744). Aborting now... war133:/etc/init.d # ./pandora_network start Pandora FMS Network Server is currently running on this machine with PID (4747). Aborting now... war133:/etc/init.d # ./pandora_network start Pandora FMS Network Server is currently running on this machine with PID (4750). Aborting now... war133:/etc/init.d # ./pandora_network start Pandora FMS Network Server is currently running on this machine with PID (4753). Aborting now... war133:/etc/init.d # ./pandora_network start Pandora FMS Network Server is currently running on this machine with PID (4756). Aborting now... war133:/etc/init.d # ./pandora_network start Pandora FMS Network Server is currently running on this machine with PID (4759). Aborting now... The funny thing is that 'pid -x /path/to/pandora' from shell returns nothing. It seems garbege is returned only inside script... Note: this has probably something to do with the fact that on Suse init.d = rc.d

  2. You can use the old scripts for that matters, which don't depend on pidof. There's a thread opened regarding this issue: (Link not available anymore)

Entra en tu cuenta para publicar.