[opensuse] What is Lchown? (rsnapshot)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm testing rsnapshot, a perl utility to do backups, included with opensuse 10.3 It fails, does nothing; very verbose output follows: 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:~ # It claims to success in under a second, without backing up a single file! That's not a good thing for a backup program. IMNSHO it is Horribly Bad that it claims success with a non existing backup! What on earth is that Lchown? I can't find it with pin. Could it be "perl-lchown", which is not included in the distro? If that is so, I assume it is a packaging bug that the rpm for a required package is not included, not even "required". - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHnNWitTMYHG2NR9URAkYCAJ9jWOAdOgBVc++jOAx05oEgaw1megCfX5No aXb9WPqJQfTUAFrmnQ+eato= =Y31x -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Jan 27, 2008 9:03 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Lchown module not found What on earth is that Lchown? I can't find it with pin. Could it be "perl-lchown", which is not included in the distro?
If that is so, I assume it is a packaging bug that the rpm for a required package is not included, not even "required".
Yes, Lchown is Perl module from CPAN - Lchown - use the lchown(2) system call from Perl. Packaging bug definitely. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I'm testing rsnapshot, a perl utility to do backups, included with opensuse 10.3
It fails, does nothing; very verbose output follows:
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:~ #
It claims to success in under a second, without backing up a single file! That's not a good thing for a backup program. IMNSHO it is Horribly Bad that it claims success with a non existing backup!
What on earth is that Lchown? I can't find it with pin. Could it be "perl-lchown", which is not included in the distro?
If that is so, I assume it is a packaging bug that the rpm for a required package is not included, not even "required".
LCHOWN(P) POSIX Programmer's Manual LCHOWN(P) NAME lchown - change the owner and group of a symbolic link SYNOPSIS #include <unistd.h> int lchown(const char *path, uid_t owner, gid_t group); DESCRIPTION The lchown() function shall be equivalent to chown(), except in the case where the named file is a symbolic link. In this case, lchown() shall change the ownership of the symbolic link file itself, while chown() changes the ownership of the file or directory to which the symbolic link refers. RETURN VALUE Upon successful completion, lchown() shall return 0. Otherwise, it shall return -1 and set errno to indicate an error. blah blah blah. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----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 :-/ 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! 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". 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 - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHnbehtTMYHG2NR9URAjKqAJ94KzpkAlYJYHvn1IwRcA3rQjiv2gCfeu0F /LL2IVfOVYXJcIkD/Pjhq4E= =uljK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 * Carlos E. R. <robin.listas@telefonica.net> [01-27-08 14:18]:
What on earth is that Lchown? I can't find it with pin. Could it be "perl-lchown", which is not included in the distro?
look at: http://anorien.warwick.ac.uk/mirrors/opensuse/guru/packages/Libraries/perl-l... - -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFHnRvKClSjbQz1U5oRAvvDAJ45x3gms5FvPgkcIiiht8EHN2/KagCfenJZ 5XwDPoqgTWArxJz39mtkSxY= =pa4D -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-01-27 at 19:03 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [01-27-08 14:18]:
What on earth is that Lchown? I can't find it with pin. Could it be "perl-lchown", which is not included in the distro?
look at:
http://anorien.warwick.ac.uk/mirrors/opensuse/guru/packages/Libraries/perl-l...
I have also seen it in http://download.opensuse.org/repositories/Archiving:/Backup/openSUSE_10.3 but I'm very hesitant and disgusted needing a non standard repo to use a standard rpm. (I'm trying to open a bugzilla, but the server is down) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHnSZRtTMYHG2NR9URAmhNAJ9vQRbg3Ktq9JETgu9SMJZvdopgQwCfTdZj 41yOTyMEvVpClKOQyRqW0sQ= =JErW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Sunday 2008-01-27 at 19:03 -0500, Patrick Shanahan wrote:
* Carlos E. R. <> [01-27-08 14:18]:
What on earth is that Lchown? I can't find it with pin. Could it be "perl-lchown", which is not included in the distro?
look at:
http://anorien.warwick.ac.uk/mirrors/opensuse/guru/packages/Libraries/perl-l...
I have also seen it in http://download.opensuse.org/repositories/Archiving:/Backup/openSUSE_10.3
but I'm very hesitant and disgusted needing a non standard repo to use a standard rpm.
(I'm trying to open a bugzilla, but the server is down)
-- Cheers, Carlos E. R.
Unfortunately the underlying issue is a little worse (at least with 10.2). Try running cpan -O and you will begin to understand the problem. Many of the SuSE 10.2 Perl module RPMs from packman are badly out of date. The SuSE Perl stuff is a bit better but still lags (as would be expected). Only spotted problem when SuSE servers were down and was checking out what I thought were issues with a Perl Module to find that my current version of the module was 2 major releases out of sync. I think in future I will probably maintain my Perl stuff from CPAN. (The nuisance is that for compiled Perl modules one needs to install the devel RPMs relevant to the module). - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHnbnyasN0sSnLmgIRAieXAJ9QkymIKGgynBFqEYp6jUeUbXgaRgCgnqK+ N4F0A6UJEoM+YzLcWInAz4U= =qitj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
I think in future I will probably maintain my Perl stuff from CPAN. (The nuisance is that for compiled Perl modules one needs to install the devel RPMs relevant to the module).
FWIW, that's what I've done for years and generally without any issues at all. Very occasionally an underlying compiled library from the Suse distribution is so old that the current CPAN release can't deal with it, but usually the CPAN modules will cope with binary libraries that are considerably older than themselves. To a large extent, these occasional difficulties are self-inflicted because I run Suse releases way past their sell-by-date. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-01-28 at 11:18 -0000, G T Smith wrote:
Unfortunately the underlying issue is a little worse (at least with 10.2). Try running cpan -O and you will begin to understand the problem. Many of the SuSE 10.2 Perl module RPMs from packman are badly out of date. The SuSE Perl stuff is a bit better but still lags (as would be expected).
Yes, but for a non perl guy like me, I'd better stick to the rpms. The worst thing, for me, is that the "rsnapshot" application does an examination of itself without discovering any problem, does the backup claiming sucess, and fails to save anything. That's the worst thing, IMO. I can not trust a backup application that claims success after failing completely. :-/ I'll have to search for another one. Perhaps dirvish. Dunno. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHncP0tTMYHG2NR9URAlEaAJ9s7w3udUtifob8sSpjmLbG9x5gAQCfaAZ7 7cG3Sh5/aWfWAI4aovtNBnk= =6jNr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
The Monday 2008-01-28 at 11:18 -0000, G T Smith wrote:
<snip>
Yes, but for a non perl guy like me, I'd better stick to the rpms.
Unfortunately, I am getting the impression that the non-SuSE rpm variants are not terribly well synchronised (a couple introduced minor problems which only disappeared when I bit the bullet and did a full perl module update from CPAN), and the official Perl RPMs are a bit limited in scope. I think it might be good idea for CPAN support for Perl, possibly PEAR support for PHP and whatever the Python community use to be integrated into YaST. With YaST identifying the appropriate development RPMs and installing them as required. This would help non-Perl,php,Python people maintain their installations in these languages and could be of benefit for those who choose to work with these languages. AFAIK there is no cpan equivalent for checkinstall, so generating an RPM from a cpan install is unlikely to be straightforward.
The worst thing, for me, is that the "rsnapshot" application does an examination of itself without discovering any problem, does the backup claiming sucess, and fails to save anything. That's the worst thing, IMO.
I can not trust a backup application that claims success after failing completely. :-/
I agree.. It could be a packaging issue, it could also be a mixture of Perl module versions which does not quite work as expected (and you cannot really blame the developer for that), or both.
I'll have to search for another one. Perhaps dirvish. Dunno.
Which is why I am working on something initially for my own use.
-- Cheers, Carlos E. R.
- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHndS+asN0sSnLmgIRAj45AJ9miMMevl3HtO3Uf0HLB/QdbR4yaQCgvwtD 18JGD7CTKLlp6y8jcuYE21o= =u6Rh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-01-28 at 13:12 -0000, G T Smith wrote:
I can not trust a backup application that claims success after failing completely. :-/
I agree..
It could be a packaging issue, it could also be a mixture of Perl module versions which does not quite work as expected (and you cannot really blame the developer for that), or both.
I've no idea. I did what I could: write a Bugzilla.
I'll have to search for another one. Perhaps dirvish. Dunno.
Which is why I am working on something initially for my own use.
I'm making do using rsync directly: rsync -av --link-dest=$PWD/prior_dir host:src_dir/ new_dir/ - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHnmB0tTMYHG2NR9URAqYGAJ491r4F0ARDQdE7Ief0M3uKGGd5dgCffhZr QlfaP9BHj9A7YRu05vYh5M8= =VILz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Aaron Kulkis -
Carlos E. R. -
Dave Howorth -
G T Smith -
Mark Goldstein -
Patrick Shanahan