This is a respose to both Juerd and crenz so I'll put the node here.
# # the short name by which your service will be known (cannot be 'my')
# Please document *why* something is not possible, instead of just "can't do this".
Because otherwise PerlSvc would not be able to read it.
# Do check the return values. In a module, it's better to turn PrintError off and handle errors yourself.
This ain't a module. The PerlSvc tool requires that the service name and the callbacks are in package PerlSvc. I think the info should contain a pointer to the PerlSvc docs and the "Perl Development Kit" should also be mentioned to prevent confusion.
Jenda
Always code as if the guy who ends up maintaining your code
will be a violent psychopath who knows where you live.
-- Rick Osborne
Edit by castaway: Closed small tag in signature
In reply to Re: Service monitor with Perl and PerlSvc
by Jenda
in thread Service monitor with Perl and PerlSvc
by perlsage
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |