Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Sunday 2008-01-27 at 18:25 -0500, Aaron Kulkis wrote:
nimrodel:~ # rsnapshot daily
require Lchown <========
Lchown module not found
Setting locale to POSIX "C"
echo 3970 > /var/run/rsnapshot.pid
rm -f /var/run/rsnapshot.pid
/bin/logger -i -p user.info -t rsnapshot /usr/bin/rsnapshot daily: \
completed successfully
nimrodel:~ #
LCHOWN(P) POSIX Programmer's Manual
LCHOWN(P)
Yes, but that's the C library function, not the perl module it is
looking for.
int lchown(const char *path, uid_t owner, gid_t group);
The worst thing is that the program does a check of internal consistency
and needed extensions, proclaims that everything is perfect, I go ahead
attempting a backup, it claims sucess, and nothing was saved :-/
Ouch. Serious lack of error-checking there.
Just imagine this was a cron job. The sysadming has a brief look at the
logs, sees "sucess", and thinks the daily/hourly backup is alright.
But there is nothing saved! Not a hint there is something wrong!
That's why a good sysadmin always tests by restoring a few
files from a backup, just to make sure that the script is
actually doing what he thinks it is.
Notice that at the default level of verbosity, there is no mention of
lchown being missed; the logged output is the single line "completed
successfully".
if lchown just changes ownership of a link...what does
the link point at, and what (if anything) is there?
The above output with the error is a fully verbose output. This is the
default output:
Jan 28 03:07:08 nimrodel rsnapshot[14933]: /usr/bin/rsnapshot daily:
completed successfully
Hmm
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
