Closed xeyownt closed 7 years ago
borgcronic uses $$ to store the PID of the process owning the lock and as ID in syslog. This PID is not correct when the daemon forks itself to start the main backup process. In that case, $$ is the PID of the parent process, not of the child.
$$
The fix is to always use $BASHPID.
$BASHPID
borgcronic uses
$$
to store the PID of the process owning the lock and as ID in syslog. This PID is not correct when the daemon forks itself to start the main backup process. In that case,$$
is the PID of the parent process, not of the child.The fix is to always use
$BASHPID
.