search

ajrockefeller / openfpc

Automatically exported from code.google.com/p/openfpc
0 stars 0 forks source link

PID file issues - openpfc-0.5 #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 

Couple of things...

1. The openfpc-daemonlogger pid file currently goes to /var/run which is 
correct. The openfpc-queued pid file goes to /tmp (maybe because of the 
SAVEDIR= setting???) this pid file should probably go to /var/run by default.

2. Both openfpc-daemonlogger and openfpc-queued should provide a way in the 
conf file to define the pid path and name. This would make writing distro 
specific init scrips a lot easier.

Original issue reported on code.google.com by Jason.R....@gmail.com on 25 Mar 2011 at 3:14

GoogleCodeExporter commented 8 years ago 
Agreed.

Original comment by leon.j.w...@gmail.com on 25 Mar 2011 at 4:18

GoogleCodeExporter commented 8 years ago 
adding a -p -P to the openfpc would be even better.

ex.

openfpc -a start -t openfpc-daemonlogger -P /var/run -p openfpc-daemonlogger.pid

Original comment by Jason.R....@gmail.com on 25 Mar 2011 at 5:28

GoogleCodeExporter commented 8 years ago 
I was a little confused when I spotted this bug because I was surprised to 
think that I would have hard-coded a PID path (especially to /tmp). You can set 
the PID PATH via the config file. E.g.

PIDPATH=/some/path

The default is (or rather was) /tmp, now set to /var/run. The filename is 
openfpc-queued-<NODENAME>.pid.
I've also added the PIDPATH value to the config file to announce it's existence.

Sending        OFPC/Config.pm
Sending        etc/openfpc-default.conf
Sending        etc/openfpc-example-proxy.conf
Transmitting file data ...
Committed revision 282.

-Leon

Original comment by leon.j.w...@gmail.com on 27 Mar 2011 at 5:55