Re: fw_update lock_db should exit when parent exits

2023-08-24 Thread Andrew Hewus Fresh
On Thu, Aug 24, 2023 at 06:53:27AM -0600, Todd C. Miller wrote: > On Wed, 23 Aug 2023 18:23:40 -0700, Andrew Hewus Fresh wrote: > > > I would have to see an example of doing that between ksh and perl. > > Standard output should already be a pipe in the perl process by > virtue of running as a co-

Re: fw_update lock_db should exit when parent exits

2023-08-24 Thread Todd C . Miller
On Wed, 23 Aug 2023 18:23:40 -0700, Andrew Hewus Fresh wrote: > I would have to see an example of doing that between ksh and perl. Standard output should already be a pipe in the perl process by virtue of running as a co-process. In theory you should be able to poll on it checking for POLLHUP.

Re: fw_update lock_db should exit when parent exits

2023-08-23 Thread Andrew Hewus Fresh
On Wed, Aug 23, 2023 at 08:42:03AM -0600, Todd C. Miller wrote: > On Tue, 22 Aug 2023 19:55:56 -0700, Andrew Hewus Fresh wrote: > > > I noticed this when testing how signal handling worked in fw_update, it > > turns out that if you `pkill -KILL -f fw_update` it may leave behind a perl > > process

Re: fw_update lock_db should exit when parent exits

2023-08-23 Thread Todd C . Miller
On Tue, 22 Aug 2023 19:55:56 -0700, Andrew Hewus Fresh wrote: > I noticed this when testing how signal handling worked in fw_update, it > turns out that if you `pkill -KILL -f fw_update` it may leave behind a perl > process that is locking the package database. Instead of just waiting > to be kil

Re: fw_update lock_db should exit when parent exits

2023-08-22 Thread Lucas
Andrew Hewus Fresh wrote: > I noticed this when testing how signal handling worked in fw_update, it > turns out that if you `pkill -KILL -f fw_update` it may leave behind a perl > process that is locking the package database. Instead of just waiting > to be killed, we can have that process check

Re: fw_update lock_db should exit when parent exits

2023-08-22 Thread A Tammy
On 8/22/23 22:55, Andrew Hewus Fresh wrote: > I noticed this when testing how signal handling worked in fw_update, it > turns out that if you `pkill -KILL -f fw_update` it may leave behind a perl > process that is locking the package database. Instead of just waiting > to be killed, we can have

fw_update lock_db should exit when parent exits

2023-08-22 Thread Andrew Hewus Fresh
I noticed this when testing how signal handling worked in fw_update, it turns out that if you `pkill -KILL -f fw_update` it may leave behind a perl process that is locking the package database. Instead of just waiting to be killed, we can have that process check to see if its parent is still aroun