| 1 |
On Wednesday 25 November 2015 22:29:52 waltdnes@××××××××.org wrote: |
| 2 |
> I'm getting a bunch of messages like... |
| 3 |
> |
| 4 |
>> Subject: cron for user root root [ ! -x /etc/cron.hourly/0anacron ] |
| 5 |
>> && { test -x /usr/sbin/run-crons && /usr/sbin/run-crons ; } |
| 6 |
>> |
| 7 |
>> /bin/sh: root: command not found |
| 8 |
> |
| 9 |
>/bin/sh does exist... |
| 10 |
> |
| 11 |
>[d531][waltdnes][~] ll /bin/sh |
| 12 |
>lrwxrwxrwx 1 root root 4 Nov 24 12:10 /bin/sh -> bash |
| 13 |
> |
| 14 |
>/etc/ cron.hourly cron.weekly cron.monthly are empty except for a |
| 15 |
>dummy file .keep_sys-process_cronbase-0 |
| 16 |
|
| 17 |
I remember from experience that those messages are misleading. It's not dcron |
| 18 |
complaining about /bin/sh not existing, it's /bin/sh complaining about some |
| 19 |
command not existing. In fact, bash's error message format indicates that |
| 20 |
something is trying to execute "root": |
| 21 |
|
| 22 |
% bash -c "echl" |
| 23 |
bash: echl: Kommando nicht gefunden. |
| 24 |
|
| 25 |
(dash's error message would look like this: |
| 26 |
% dash -c "echl" |
| 27 |
dash: 1: echl: not found) |
| 28 |
|
| 29 |
HTH |
| 30 |
-- |
| 31 |
Marc Joliet |
| 32 |
-- |
| 33 |
"People who think they know everything really annoy those of us who know we |
| 34 |
don't" - Bjarne Stroustrup |
Archives