From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dcron problem on new install
Date: Thu, 26 Nov 2015 08:09:31 +0100 [thread overview]
Message-ID: <3942764.ktA4vNC8y0@thetick> (raw)
In-Reply-To: <20151126032952.GA16046@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
On Wednesday 25 November 2015 22:29:52 waltdnes@waltdnes.org wrote:
> I'm getting a bunch of messages like...
>
>> Subject: cron for user root root [ ! -x /etc/cron.hourly/0anacron ]
>> && { test -x /usr/sbin/run-crons && /usr/sbin/run-crons ; }
>>
>> /bin/sh: root: command not found
>
>/bin/sh does exist...
>
>[d531][waltdnes][~] ll /bin/sh
>lrwxrwxrwx 1 root root 4 Nov 24 12:10 /bin/sh -> bash
>
>/etc/ cron.hourly cron.weekly cron.monthly are empty except for a
>dummy file .keep_sys-process_cronbase-0
I remember from experience that those messages are misleading. It's not dcron
complaining about /bin/sh not existing, it's /bin/sh complaining about some
command not existing. In fact, bash's error message format indicates that
something is trying to execute "root":
% bash -c "echl"
bash: echl: Kommando nicht gefunden.
(dash's error message would look like this:
% dash -c "echl"
dash: 1: echl: not found)
HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-26 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 3:29 [gentoo-user] dcron problem on new install waltdnes
2015-11-26 7:09 ` Marc Joliet [this message]
2015-11-26 7:49 ` J. Roeleveld
2015-11-26 10:47 ` Jeremi Piotrowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3942764.ktA4vNC8y0@thetick \
--to=marcec@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox