Yesterday I used Yast2 (the /etc/sysconfig part) to make a couple changes in locate and autoupdate. Later, when the daily crons ran, it showed errors when running those to cron jobs... errors that kept the jobs from completing. To make a long story short, it created /etc/sysconfig/autoupdate and /etc/sysconfig/locate with bad syntax... it created variable/value pairs that looked like this: VALUE = something That *should* be: VALUE="something" If it isn't formatted without spaces and with the quotation marks, when the cron job script runs and tries to source the /etc/sysconfig/locate file, it sees "VALUE" as a command and cannot find such a command, instead of coming back with $VALUE being set to something. It also failed to produce complete files with all variables, for instance "RUN_UPDATEDB" wasn't in the file, it only contained two lines, the malformatted RUN_UPDATEDB_AS and UPDATEDB_PRUNEPATHS lines discussed above. Those also happen to be the only values I modified with Yast2. I was able to fix it by copying template files from /var/adm/fillup-templates/sysconfig.autoupdate and sysconfig.locate and then edit them by hand. Watch out if you use Yast2 in 10.0 to make changes like this... it's broken. Michael -- San Francisco, CA
On Sun, Oct 23, 2005 at 07:21:22AM -0700, Michael Nelson wrote:
VALUE = something
That *should* be:
VALUE="something"
If it isn't formatted without spaces and with the quotation marks, when the cron job script runs and tries to source the /etc/sysconfig/locate file, it sees "VALUE" as a command and cannot find such a command, instead of coming back with $VALUE being set to something.
Sorry, the quotes aren't neccessary unless "something" contains whitespace. But the whitespace between VALUE and = and something do break the config. BTW, checking some more, I found the same thing happened to every file in /etc/sysconfig that was touched by the Yast2 editing. Michael -- San Francisco, CA
participants (1)
-
Michael Nelson