Custom Query (196 matches)

(Imported from ​help.mit.edu #433591.)

At the moment, if you run cronload with no arguments, it'll give you an error message from cat, and wipe your crontab:

[asa@cats-whiskers]:~/Scripts/django/db2.0/asadb$ cronload
/bin/cat: : No such file or directory
New crontab for asa:

[asa@cats-whiskers]:~/Scripts/django/db2.0/asadb$ 

Instead, it should give you a nice error message and not touch your crontab, or something.

On conan-obrien

/etc/cron.daily/logrotate:
kill: 91: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
error: error running non-shared postrotate script for /var/log/conserver/bees-knees.log of '/var/log/conserver/*.log '
kill: 91: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
error: error running non-shared postrotate script for /var/log/conserver/miracle-cure.log of '/var/log/conserver/*.log '
kill: 91: Usage: kill [-s sigspec | -signum | -sigspec] [pid | job]... or
kill -l [exitstatus]
error: error running non-shared postrotate script for /var/log/conserver/server.log of '/var/log/conserver/*.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

The trouble is that /var/run/conserver.pid no longer has a pid in it. But this is not the case for david-letterman. Quite vexing.