I'm running 7.0.4.
Here's an example...
(before backup)
# ls -ld /bin
dr-xr-xr-x 2 root root 4096 Jul 22 09:56 /bin
# ls -l /bin/ping
-rwsr-xr-x 1 root root 40760 Sep 17 2013 /bin/ping
(after restore selecting file /bin/ping)
# ls -ld /bin
drwsr-xr-x 2 root root 4096 Jul 22 14:38 bin
# ls -
Sorry if I have not researched this enough before bringing it to the
list, but what I'm seeing is very odd. Someone else must have run into
this before me.
If I restore a setuid or setgid file, the file is restored without the
setuid/setgid bit set. However, the directory containing the fil
Sadly, this error is still present in v7.0.4. There is another error, too,
where there is no writeable media in the tape drive.
Fatal error: spool.c:263 Fatal append error on device "LTO5-2"
(/dev/tape-admin2): ERR=tape_dev.c:161 Unable to open device "LTO5-2"
(/dev/tape-admin2): ERR=No medium
Hello,
In my opinion, using network mounted disks for backup is a risky
business. Bacula is designed to work with direct attached disks and
tapes, so when you connect them instead by a network, you introduce more
errors (networks have more faults than direct attached devices), delays
(latency), a
