Created attachment 186828 [details] Screenshot showing errors backing up socket file types. SUMMARY If socket file types are attempted to be backed up, red error messages appear in the output. STEPS TO REPRODUCE 1. Run a backup that includes directories containing socket file types. (e.g. /run) 2. Backup finishes OK, but reports "some files were skipped" 3. There are a lot of errors saying, "Can not archive file type 'socket'" 4. Most of the reported files are in /run, /var/lib, and /tmp, which I include in my backups "just in case". OBSERVED RESULT See attachment. EXPECTED RESULT It would be nice not to see all the errors so that ACTUAL errors stand out more (if any). SOFTWARE/OS VERSIONS Rocky linux 9.6 X86_64 Kbackup version 23.08.5 - Installed from the EPEL 9 Repository. GNOME desktop 40.4.0 Wayland window system. ADDITIONAL INFORMATION Not a "KDE on GNOME" problem... Kbackup runs well on Gnome. :-) Obviously I could just exclude /run/* , /var/lib/* , and /tmp/* using filters, but that would also exclude some regular files. Am I wrong about that? Perhaps those directories never contain files that are meaningful to back up. Except perhaps /tmp which I sometimes use when moving things around. Is this addressed in a newer version? (wondering if EPEL is serving an old version.)
It does not make any sense to include /run in a backup, since it is a temporary file system in RAM (tmpfs) and will be gone whenever you reboot. For all other directories you back up, it seems to me a good idea to tell the user that certain files could not be backed up, hence no need for an additional profile setting.
(In reply to Martin Koller from comment #1) > It does not make any sense to include /run in a backup, since it is a > temporary file system in RAM (tmpfs) and will be gone whenever you reboot. > > For all other directories you back up, it seems to me a good idea to tell > the user that certain files could not be backed up, hence no need for an > additional profile setting. Thank you. I apologize for my ignorance regarding the /run filesystem.