We've been discussing this problem for a while now, and I have one specific
related question left. It all seems to boil down to a shell script that
contains, among other things, these lines:
# start backup - set cron mode, set nice level to not slowdown other processes
# set server component testsuite to parse UI requests
nice -n 15 /usr/lib/YaST2/bin/y2base backup '("cron")'
'("'$PROFILE'")' testsuite > /dev/null
The messages from cron that end up in root mail look something like this:
Subject: Cron <[EMAIL PROTECTED]> /usr/lib/YaST2/bin/backup_cron
"profile=partial_backup"
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Date: Mon, 24 Dec 2007 00:01:02 -0800 (PST)
No such client module backup
Question is, where is client module 'backup' supposed to come from? One would
think that YaST would be installed with whatever modules are needed to handle
the tasks that it offers, but perhaps not? Does anyone know if there's
something more I need to install in order for this not to fail?
Thanks,
Jerry
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
