On 31/5/17 16:44, Craig Barratt wrote:
Michael is correct that BackupPC does use $Info->{pid} (which is read
from status.pl <http://status.pl>). But it does check that that
process exists before printing the error message (using perl's kill(0,
pid) that doesn't really send a signal, but tells you whether the
process is alive). So I don't know why it claims process 1289 is
running; that would mean "kill(0, 1289)" returns 1 (success)...
I assume after a reboot it is very possible that some other process is
running and has used pid 1289, and isn't a short-lived process (ie, some
other daemon or similar).
Does BPC check the name of the process that is found? This would help to
avoid this confusion (pid exists but is not a BPC pid).
P.S.: Yes, it might ultimately turn out that you need to break
down the door,
but, in my experience, you usually don't break down a
*random* door
even then.
Which means the OP broke down a random door, and didn't even need to get
into that room anyway (ie, killed a random unknown process, which may or
may not be causing other problems, since the expected process is not
running correctly).
Regards,
Adam
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
