On 8/14/2015 2:28 PM, Achim Gratz wrote:
> Jon TURNEY writes:
>> I don't understand why you need to do anything over and above what
>> setup already does.
>
> Read on.
>
>> Setup cannot replace /usr/bin/fish.exe while there is a running
>> process with it loaded, and will request permission to ki
Jon TURNEY writes:
> I don't understand why you need to do anything over and above what
> setup already does.
Read on.
> 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
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 t
> 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
> >>
On 8/13/2015 3:39 PM, Achim Gratz wrote:
> Andrew Schulman writes:
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
Andrew Schulman writes:
>> > 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, b
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
> > 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 (
Andrew Schulman writes:
> OK. Right, I have seen and used that dialog. But more often, I just notice
> that
> after an update, processes have exited. This happened to me recently with
> mintty, for example, but there have been others.
If you do an automated install, you will not be prompted.
>
> On 13/08/2015 07:19, Andrew Schulman wrote:
> > I've noticed that when I update a package, the exe's in it get killed. For
> > example, when emacs gets updated, my running emacsen die.
> >
> > Is this something that setup explicitly does, for all packages? Or that
> > some
> > packages do for
On 13/08/2015 07:19, Andrew Schulman wrote:
I've noticed that when I update a package, the exe's in it get killed. For
example, when emacs gets updated, my running emacsen die.
Is this something that setup explicitly does, for all packages? Or that some
packages do for themselves in a preremov
I've noticed that when I update a package, the exe's in it get killed. For
example, when emacs gets updated, my running emacsen die.
Is this something that setup explicitly does, for all packages? Or that some
packages do for themselves in a preremove script? Or just a byproduct of
replacing a
12 matches
Mail list logo
