samba-bugs at samba.org
2010-May-13 07:23 UTC
DO NOT REPLY [Bug 7426] New: --files-from= broken when run from crontab
https://bugzilla.samba.org/show_bug.cgi?id=7426 Summary: --files-from= broken when run from crontab Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: bgcladd at gmail.com QAContact: rsync-qa at samba.org running rsync version 3.0.7 (also tried rsync-HEAD-20100501-0829GMT) debian lenny amd64, if i call a shell script with the content: rsync -a -e 'ssh -i /home/mapsync/.ssh/id_rsa' --bwlimit=1221 --files-from=/tmp/tf2maplist --no-relative / mapsync at foo.com:/home/mapsync/tf2maps Everything runs great from a shell. /tmp/tf2maplist is a file which contains one line at a time the location of all the .bsp files found in /home, here is a snippet from /tmp/tf2maplist: /home/user1/srcds_l/orangebox/tf/maps/cp_generator_b4b.bsp /home/user2/srcds_l/orangebox/tf/maps/cp_orange_n5_final.bsp When run from the root crontab this error occurs: rsync: change_dir "/root/home/user1/srcds_l/orangebox/tf/maps" failed: No such file or directory (2) How do i stop rsync from prepending /root/ to the front of every line when run from cron? Thanks! -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
samba-bugs at samba.org
2010-May-13 16:45 UTC
DO NOT REPLY [Bug 7426] --files-from= broken when run from crontab
https://bugzilla.samba.org/show_bug.cgi?id=7426 matt at mattmccutchen.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Comment #1 from matt at mattmccutchen.net 2010-05-13 11:45 CST ------- *** This bug has been marked as a duplicate of bug 7425 *** -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.