If you're using serctl to start ser, it should be setting the pid location properly... but the init.d ser script does not make ser create the pid file. The solution I used was to add OPTIONS="-P /var/run/ser.pid" after the RETVAL line in the init.d/ser script.
On 7/29/05, Colin Jordan cjordan@econetwireless.com wrote:
I cannot control SER via serctl stop/start due to the fact that when it runs via this command it is not finding a ser.pid. I have searched for ser.pid on my system and it is not there (was just making sure that serctl was not looking in the wrong spot for the PID file). Any suggestions??