Ævar Arnfjörð Bjarmason wrote:
Why does this happen?
---------- Forwarded message ----------
From: Cron Daemon <root(a)cassini.toolserver.org>
Date: Sat, Nov 14, 2009 at 11:35 AM
Subject: Cron <root@cassini> /sql/diffs/load-next
To: root(a)cassini.toolserver.org
ERROR: List of process IDs must follow -p.
********* simple selection ********* ********* selection by list *********
-A all processes -C by command name
-N negate selection -G by real group ID (supports names)
-a all w/ tty except session leaders -U by real user ID (supports names)
-d all except session leaders -g by session OR by effective group name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options ***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy
Some ps call in the script /sql/diffs/load-next run by cron uses the
wrong syntax, erroring out. Cron emails you so you can fix it.
ps has an odd syntax. Bsd syntax, posix syntax, and so on.
Steps in order to fix it:
-Find the ps call that produces the error.
-Detect the equivalent working syntax.
-Change the script.