otpd should support writing its own PID files.

[GoogleCodeExporter]

otpd is hard to support in usual start/stop init scripts because it doesn't 
create pid files like other normal daemons.

Support for this should be added.  Right now the only "good" way to do this is 
to either run with otpd -f and make your own PID file (which breaks logging 
via syslog), or use evil things like pkill in your stop scripts which search 
for 
the otpd process in ps(1).

Original issue reported on code.google.com by b...@google.com on 12 Feb 2010 at 12:49

• Blocking: 3.3.0 master issue #14

[GoogleCodeExporter]

Original comment by fr...@gmail.com on 9 Aug 2010 at 11:08

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by fr...@gmail.com on 26 Aug 2010 at 7:49

• Added labels: Milestone-Release3.3.0

[GoogleCodeExporter]

I have added support for this, see the attached patch. 

Original comment by djne...@gmail.com on 6 May 2011 at 9:39

Attachments:

• pidfile.patch