Kevin,
The getwd usually means that you're (or cron) is trying to do something
from a directory that doesn't exist.
Example,
cd /usr/trash
Then in another xterm or VC, type rmdir /usr/trash
Now in the first xterm or VC, type "ls" or "cd .." and you should
get the getcd error. You can then cd /tmp or whatever to get back
to normal.
I'd look over the scripts in /etc/cron.daily and see if any of them
are trying to do something from a specific directory.
Are each of the scripts using #!/bin/sh or maybe some other
shell that has been removed? Maybe #!/bin/sh is typo'd ?
My thoughts,
Rick
On Tue, 26 May 1998, Kevin A. Pieckiel wrote:
> I don't have the slightest clue where the problem is. I get this
> message daily and it's getting annoying. Any clues? Suggestions
> welcome:
>
>
> >From [EMAIL PROTECTED] Tue May 26 08:05:07 1998
> Date: Tue, 26 May 1998 01:02:01 -0400
> From: Cron Daemon <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Cron <root@gateway> run-parts /etc/cron.daily
>
> shell-init: could not get current directory: getwd: cannot access parent directories
> job-working-directory: could not get current directory: getwd: cannot access parent
>directories
>
> Kevin A. Pieckiel
>
>
--
Rick L. Mantooth [EMAIL PROTECTED]
http://www.why.net/users/rickdman/index.html
Love: two vowels, two consonants, two fools.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
