Bug#153547: start-stop-daemon: pid_is_exec may fails to achieve its goal
Without a "broken package", I can find one case where the inode change will be
- foo is a daemon started with perl (or python, java, etc.).
- the init script for foo uses '--exec /path/to/perl' to make s-s-d make the
- foo is started
- perl is upgraded
- after this, the init script will fail stopping/restarting foo
I admit this is some kind of corner case, but really the inode change is
something that can happen sometimes during system operation : moving/replacing
files, backuping, mouting something over /usr when changing partition layout, etc.
Perhaps I'm missing something somewhere, but what's the point of checking
the inode ? How is it better than checking the path ?
== Thomas Morin -- GSM: 06 83 20 64 87 -- Tel: 02 98 05 98 54
== firstname.lastname@example.org -- email@example.com
== PGP Id:8CEA233D Key FP:503BF6CFD3AE8719377B832A02FB94E08CEA233D
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com