On Monday morning, I had eight emails each notifying me of a failed rsync attempt. This is one of those messages: From: Cron Daemon <rsyncer@pg02.int.unixathome.org> To: dan@langille.org Subject: Cron <rsyncer@pg02> ~/bin/backup.sh > /dev/null X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <MAILTO=dan@langille.org> X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:$HOME/bin; export PATH> X-Cron-Env: <LOGNAME=rsyncer> X-Cron-Env: <USER=rsyncer> Date: Mon, 25 May 2026 02:02:00 +0000 Message-Id: <6a13ad98.43eb8.34b50ce7@pg02.int.unixathome.org> /usr/local/sbin/rrsync error: unsafe arg: / ['', '/usr/home/rsyncer/backups'] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(232) [Receiver=3.4.3] Well, that’s a new one to me. This post will eventually show you the solution, and if that’s what you need now, jump to the bottom. If you’re not in a rush, I’m…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.