do package updates automatically kill running exes?

[Jon TURNEY]

On 14/08/2015 12:35, Andrew Schulman wrote:
>> On 13/08/2015 20:02, Andrew Schulman wrote:
>>>>> Anyway, that answers my question.  If I want to be sure a process from one of my
>>>>> packages exits, I need to put a killall into its preremove script.
>>>>
>>>> I've put a "pkill ." in all scripts that run setup (with the requisite
>>>> are you sure? y/N).
>>>
>>> Ugh, both psmisc (killall) and procps (pkill) aren't in base, so both of
>>> those may fail.
>>
>> What problem are you trying to solve here?
>
> fish 2.2, when it comes out, will throw scary-looking errors and maybe
> malfunction if any exes from fish 2.1.1 are still running.  In particular fish
> 2.1.1 runs fishd to share environment variables between instances.  fish 2.2
> doesn't use fishd, and will throw errors if any instances of fishd are still
> running.
>
> So IMO the best option will be to killall fish in the preremove script for fish
> 2.1.1.  I think the cost of having to restart your shell is pretty low, and will
> be better than having users puzzle through the error messages from fish 2.2.

I don't understand why you need to do anything over and above what setup 
already does.

Setup cannot replace /usr/bin/fish.exe while there is a running process 
with it loaded, and will request permission to kill those processes 
before trying to replace it (and if denied, schedule a replacement for 
the next reboot)