Package: backuppc
Version: 3.2.1-4
Severity: important
Hi Ludovic,
while debugging some issues with aborted backups, I stumbled over the
following typo in /usr/share/backuppc/bin/BackupPC_dump:
1065 # Send ALRMs to BackupPC_tarExtract if we are using it
1066 #
1067 if ( $tarPid > 0 ) {
1068 kill($bpc->sigName2num("ARLM"), $tarPid);
^^
It seems to be only typo of this kind in the package:
# dgrep -n ARLM backuppc
/usr/share/backuppc/bin/BackupPC_dump:1068:
kill($bpc->sigName2num("ARLM"), $tarPid);
#
I'm not sure if that typo causes our issues here, at least I don't see
that typo in the logs.
But misspelling a signal can cause quite severe behaviour changes of a
program in general, since either the wrong or no signal at all may be
sent.
(Not sure what of those two things would happen. "perldoc -f kill"
mentions that a signal of zero would send no signal, so if that string
is not defined as signal, I'd say it results in zero when being parsed
as integer.)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
