Steve White wrote: > Hi, > > I'm getting such errors from rdiff-backup 1.0.5 in a SL 4.5 system: > SpecialFileError var/lib/mysql/mysql.sock Socket error: AF_UNIX path > too long SpecialFileError var/run/dbus/system_bus_socket Socket > error: AF_UNIX path too l ong > > There have been several discussions on this list concerning this. Of > course it is questionable to back up sockets, so there was advice to > use --exclude-sockets,
Hi Steve, I don't think any users have had trouble with --exclude-sockets recently. From what I can tell, any further errors after using that option were entirely unrelated to sockets. If you are seeing SpecialFileError's, those errors should be recoverable. That is, rdiff-backup does finish correctly, doesn't it? If it does, then you have nothing to worry about, and can indeed continue *without* using the --exclude-sockets option. What happens is this: rdiff-backup tries to make the socket, encounters the AF_UNIX error, recovers by storing information about the socket in the mirror_metadata, and then logs the SpecialFileError. On restore, rdiff-backup will attempt to recreate the socket by using the stored metadata. If rdiff-backup is *not* finishing correctly, please send the complete error message, as it is most likely not due to the AF_UNIX message. Please see http://www.nongnu.org/rdiff-backup/error_policy.html Best, Andrew -- Andrew Ferguson - [EMAIL PROTECTED] _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
