&untaint_argv; #what it sounds like (eww)
use vars qw(%opt);
-getopts("p:a:d:vsy:n", \%opt);
+getopts("p:a:d:vl:sy:nm", \%opt);
my $user = shift or die &usage;
adminsuidsetup $user;
use FS::Cron::bill qw(bill);
bill(%opt);
+#what to do about the below when using -m? that is the question.
+
use FS::Cron::notify qw(notify_flat_delay);
notify_flat_delay(%opt);
+use FS::Cron::expire_user_pref qw(expire_user_pref);
+expire_user_pref();
+
use FS::Cron::vacuum qw(vacuum);
vacuum();
=head1 SYNOPSIS
- freeside-daily [ -d 'date' ] [ -y days ] [ -p 'payby' ] [ -a agentnum ] [ -s ] [ -v ] user [ custnum custnum ... ]
+ freeside-daily [ -d 'date' ] [ -y days ] [ -p 'payby' ] [ -a agentnum ] [ -s ] [ -v ] [ -l level ] [ -m ] user [ custnum custnum ... ]
=head1 DESCRIPTION
-v: enable debugging
+ -l: debugging level
+
+ -m: Experimental multi-process mode uses the job queue for multi-process and/or multi-machine billing.
+
user: From the mapsecrets file - see config.html from the base documentation
custnum: if one or more customer numbers are specified, only bills those