On Thu, 25 Jan 2001, root wrote:
>I keep receiving this message but I don't know what's wrong with it
>Has anyone experienced anythink like that?
>Many thanks
>----- Original Message -----
>From: "Cron Daemon" <[EMAIL PROTECTED]>Subject: Cron <root@ns1>
>run-parts --report /etc/cron.daily
>
>
>> /etc/cron.daily/cfengine:
>> cf:ns1:/etc/cfengine/cfengine.conf:26: parse error
>> cfengine:ns1::26: Warning: actionsequence is empty
>> cfengine:ns1::26: Warning: perhaps cfengine.conf has not yet been set up?
>> cfengine:ns1::Execution terminated after parsing due to errors in program
>> /etc/cron.daily/cnews:
>> shell-init: could not get current directory: getcwd: cannot access parent
>directories
>> job-working-directory: could not get current directory: getcwd: cannot
>access parent directories
>> shell-init: could not get current directory: getcwd: cannot access parent
>directories
>> job-working-directory: could not get current directory: getcwd: cannot
>access parent directories
>> shell-init: could not get current directory: getcwd: cannot access parent
>directories
>> job-working-directory: could not get current directory: getcwd: cannot
>access parent directories
>> job-working-directory: could not get current directory: getcwd: cannot
>access parent directories
>> job-working-directory: could not get current directory: getcwd: cannot
>access parent directories
>> shell-init: could not get current directory: getcwd: cannot access parent
>directories
>> cd_links: could not get current directory: getcwd: cannot access parent
>directories
>> job-working-directory: could not get current directory: getcwd: cannot
>access parent directories
>> shell-init: could not get current directory: getcwd: cannot access parent
>directories
>> cd_links: could not get current directory: getcwd: cannot access parent
>directories
>>

Call alaire tech support.

-- 
***********************************
Matthew H Patterson
Unix Systems Administrator
National Support Center, LLC
Naperville, Illinois, USA
***********************************

Reply via email to