Platform: Debian Linux 6.0
Version: 1.2.1-6
The backup type executed was a backup to disk run by root. This occurs when the
backup completes successfully and also (I believe) when the command is terminated early
by the SIGKILL signal(Control-C). Most of the time, the directories left are empty but sometimes
they contain a file with the following contents:
root@mymachine ~ # cat /tmp/flexbackup.24342.mymachine/collectexit.24342.sh
#!/bin/sh
"$@"
[ $? = 0 ] || echo $@ >> /tmp/flexbackup.24342.mymachine/exitstatus.24342
root@mymachine ~ #
Here are the relevant permissions:
root@mymachine ~ # ls -ld /tmp/flexbackup.2*
drwxr-x--- 2 root root 4.0K Jan 22 05:18 /tmp/flexbackup.24342.mymachine/
drwxr-x--- 2 root root 4.0K Jan 22 05:18 /tmp/flexbackup.24428.mymachine/
drwxr-x--- 2 root root 4.0K Jan 22 05:34 /tmp/flexbackup.24954.mymachine/
drwxr-x--- 2 root root 4.0K Jan 22 05:34 /tmp/flexbackup.25012.mymachine/
drwxr-x--- 2 root root 4.0K Jan 22 05:34 /tmp/flexbackup.25036.mymachine/
root@mymachine ~ # ls -ld /tmp
drwxrwxrwt 13 root root 4.0K Jan 24 04:27 /tmp/
root@mymachine ~ # ll /tmp/flexbackup.2*
/tmp/flexbackup.24342.mymachine:
total 4.0K
-rwxr-xr-x 1 root root 85 Jan 22 05:18 collectexit.24342.sh*
root@mymachine ~ #
Maybe you can add a trap and remove $cfg::tmpdir upon receiving certain
signals(0,9, ...).
Let me know if you need anymore information.
GLS