thanks for the suggestions - it turns out i'd set SUPATH in /etc/default/cron. i assumed i could prepend $PATH (rather than full paths), and that was likely the cause of my issue. ---------- Forwarded message ---------- From: spacegoose@gmail.com <spacegoose@gmail.com> Date: Nov 19, 2006 4:55 PM Subject: Re: cron gss error To: "Casper.Dik@sun.com" <Casper.Dik@sun.com> thanks - i'd recently tried to set SUPATH=$PATH:/usr/local/bin in /etc/default/cron i suppose $PATH didn't work - i don't need it anymore anyway so i removed SUPATH - i'm guessing that was the issue. thanks! sg. On 11/19/06, Casper.Dik@sun.com <Casper.Dik@sun.com> wrote: > > >I've received the below message a few times now since machine was > >brought down by a power surge 2-3 days ago ... I can run the command > >manually (as root) with no apparent error. > > > > > >Your "cron" job on mail > >[ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean > > > >produced the following output: > > > >/usr/lib/gss/gsscred_clean[22]: rm: not found > > > Check what $PATH is for processes started by cron. > > Casper _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Mon Nov 20 08:34:53 2006
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:03 EST