X-Git-Url: http://git.freeside.biz/gitweb/?p=freeside.git;a=blobdiff_plain;f=FS%2Fbin%2Ffreeside-daily;h=f0ec9f041fa0ad59d293f0e3893ffa47b7946f57;hp=a06a2b185e4d3d72ca45c283a2d9df95ec6d2ba5;hb=eb4ff7f73c5d4bdf74a3472448b5a195598ff4cd;hpb=56be01c046fe4aad7f9a9aacc41b509483cc05f1 diff --git a/FS/bin/freeside-daily b/FS/bin/freeside-daily index a06a2b185..f0ec9f041 100755 --- a/FS/bin/freeside-daily +++ b/FS/bin/freeside-daily @@ -5,9 +5,8 @@ use Getopt::Std; use FS::UID qw(adminsuidsetup); &untaint_argv; #what it sounds like (eww) -#use vars qw($opt_d $opt_v $opt_p $opt_a $opt_s $opt_y); use vars qw(%opt); -getopts("p:a:d:vsy:", \%opt); +getopts("p:a:d:vl:sy:n", \%opt); my $user = shift or die &usage; adminsuidsetup $user; @@ -15,9 +14,14 @@ 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(); @@ -51,7 +55,7 @@ freeside-daily - Run daily billing and invoice collection events. =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 ] user [ custnum custnum ... ] =head1 DESCRIPTION @@ -69,6 +73,10 @@ the bill and collect methods of a cust_main object. See L. "pretend date" 15 days from whatever was specified by the -d switch (or now, if no -d switch was given). + -n: When used with "-d" and/or "-y", specifies that invoices should be dated + with today's date, irregardless of the pretend date used to pre-generate + the invoices. + -p: Only process customers with the specified payby (I, I, I, I, I, I, I) -a: Only process customers with the specified agentnum @@ -77,6 +85,10 @@ the bill and collect methods of a cust_main object. See L. -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