On Wed, 25 Jul 2012 13:50:32 -0700, Jeff Grossman wrote: > On Wed, 25 Jul 2012 14:25:40 +0100, Darac Marjal wrote:
(...) >>I imagine that your system shell has been changed to dash (run "ls -l >>/bin/sh" to check). Dash is somewhat stricter in its implementation of >>POSIX than bash (it's main focus is to be lighter than bash so as to >>allow quicker booting). POSIX declares that the "source" command should >>check the path when given a filename without path components. Bash >>relaxes this somewhat by also checking the current directory. Dash >>DOESN'T do this. >> >>That is, assuming somefile.sh is in the current directory, "source >>somefile.sh" will work in bash, but not dash. To fix this bashism, use >>"source ./somefile.sh". > > I just did a "grep source *" from the /etc/cron.daily directory to > figure out what file is causing me the problems. But, it came back > empty. How would I figure out where that source file is to fix it? The > e-mail is my daily cron.daily cron job e-mail that is giving me the > error. Is there any customized file/script under "/etc/cron.daily"? You can also "take a grep" into /var/log/syslog* and search for any cron.d* or per-user crontab defined routines :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jurlgv$tcf$8...@dough.gmane.org
