rsync client unable to create file in /var/run

[ijeffsc]

This seems to be failing silently on my system.

The scripts created in /var/run have logic to ensure long running cron jobs do cause duplicate runs. Specific example:

Code: Select all

if [ -r /var/run/rsync_client_running_7e5ccef4-427f-4fda-8b70-284df8e05dc0 ]; then
/usr/bin/logger -p local4.notice "Previous client synchronization still running... exiting"
exit
fi
/usr/bin/touch /var/run/rsync_client_running_7e5ccef4-427f-4fda-8b70-284df8e05dc0

This should create the "running" file in /var/run.

If the rsync client is running as an ordinary user however that user does not appear to have permission to create files in that directory. Can anyone reproduce this to verify? I believe this would be the case for any rsync configuration running as an ordinary user.

My temporary workaround is to put the ordinary user in the wheel group and modify /var/run to 775 permissions however I don't think this will survive a reboot.

[Parkcomm]

It sounds like the script does not have root privlideges

[ijeffsc]

Yes that is correct.

The rsync GUI configuration allows you to run as an ordinary user. I generally avoid root whenever possible.

When you select the ordinary user the scripts generated fail silently. For really big rsyncs especially when starting off they can run a long time and you don't want them clobbering each other. The generated scripts are pretty nice but they don't seem to account for the permissions in /var/run.

[Parkcomm]

Jeffsc - I've been travelling this week (In Port Moresby right now) and have not tried to replicate the issue. I'll give it a go on the weekend when I'm home.