On 24 Feb 2017, at 11:14, pagani laurent wrote:
Indeed -E (apple style) seems necessary to keep the files attributes
Apple is using in its standard mode (i.e. not X11).
Concerning my problem, with both Apple rsync (/usr/bin/rsync) and
Macport rsync (/opt/local/bin/rsync), the process
laucnhed via crontab starts, rsync runs but is only accessing the
backup HD in read mode and never in write mode and
its eventually hangs up. If I launch the same program by a command
line, both read and write modes are activated.
I have no idea why the crontab launch prevents rsync to write and I
don’t know how I can test that.
LP
As a user of ‘rsync’ I assume you’re familiar with the command
line. Write a small script to report your environment (‘env’)(which
will include PATH), ‘pwd’, and your UID (‘id’. ‘who’ and
‘who am i’), an ‘ls -ld’ of the backup drive mount point and its
device (like /dev/disk2s1), and a full ps list wouldn’t come amiss.
Run this directly and via cron with the o/p directed to two different
files. Compare the two and look for UIDs you don’t expect, differences
in environment variables and see if anything jumps out at you.
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com
This email sent to [email protected]
