view release on metacpan or  search on metacpan

bin/cronjob  view on Meta::CPAN

#pod   the lock was created no more than I<secs> seconds ago.
#pod * the command had any output (unless C<--errors-only>)
#pod * the command exited non-zero (always)
#pod
#pod The report will include a summary of the process and its behavior, including
#pod the time taken to run, the exit status, any signal received, and whether core
#pod was dumped.  It will also include the full (combined) output of the process.
#pod
#pod The report will be send from C<--sender> (or a reasonable default) to C<--rcpt>
#pod (or C<root>).  Its C<In-Reply-To> header will be set to a hashed value that
#pod will cause all same-subject jobs to thread together in threaded mail readers.
#pod The C<--subject> switch sets the message subject, so it's responsible for
#pod deciding which jobs thread together.  For jobs that run with variable
#pod arguments, providing a C<--subject> argument is a very good idea.
#pod
#pod =head2 locking
#pod
#pod The default lockfile name is generated with code something like this:
#pod
#pod   my $lockname = $opt->jobname || ( md5_sum( $opt->subject || $opt->command ) );
#pod   my $lockfile = sprintf '/tmp/cronjob.%s', $lockname;
#pod
#pod In other words, if you specify a C<--jobname> option, that will be used for

bin/cronjob  view on Meta::CPAN

the command exited non-zero (always)

=back

The report will include a summary of the process and its behavior, including
the time taken to run, the exit status, any signal received, and whether core
was dumped.  It will also include the full (combined) output of the process.

The report will be send from C<--sender> (or a reasonable default) to C<--rcpt>
(or C<root>).  Its C<In-Reply-To> header will be set to a hashed value that
will cause all same-subject jobs to thread together in threaded mail readers.
The C<--subject> switch sets the message subject, so it's responsible for
deciding which jobs thread together.  For jobs that run with variable
arguments, providing a C<--subject> argument is a very good idea.

=head2 locking

The default lockfile name is generated with code something like this:

  my $lockname = $opt->jobname || ( md5_sum( $opt->subject || $opt->command ) );
  my $lockfile = sprintf '/tmp/cronjob.%s', $lockname;

In other words, if you specify a C<--jobname> option, that will be used for