Separate in universal and distro-specific parts. Release to CPAN as universally consumable (maybe including e.g. an init-script only in an "examples/" dir), and create Debian-specific setup (which includes init script and logrotate hints) in a Debian package built from the CPAN release.
Seems to me that Daemon::Control is specifically for having code integrate with sysV start-stop-daemon system.
Leave it open to users of your CPAN project how to start the daemon - some may favor systemd, runit or maybe plain starting from the commandline.
Consider if relevant to also support alternate admin-controlled system-wide use (e.g. static data below /usr/local/share instead of /usr/share and dynamic data below /var/local instead of /var/lib).
If your daemons make use of external data files, consider use File::ShareDir::ProjectDistDir, or for data potentially overridable by the user consider use File::BaseDir instead.
Hope that helps :-)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.