Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Wed, Aug 16, 2017 at 7:46 AM, Guillermo Polito wrote: > > On Tue, Aug 15, 2017 at 3:25 PM, Ben Coman wrote: > >> In case any of the shutdown/startup scripts use a delay, now or in the >> future, >> I'd first try athighestPriority-1 to

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

> > From the other side I am not sure why connections should be closed when >> image is saved. In case of Seamless pool is constructed in the way that it >> checks if socket is valid before borrow it to user. > > Well, that's a seamless issue, isn't it? Did you try not subscribing > seamless to

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Wed, Aug 16, 2017 at 1:21 PM, Denis Kudriashov wrote: > 2017-08-16 12:28 GMT+02:00 Guillermo Polito : > >> >> >> On Wed, Aug 16, 2017 at 12:13 PM, Denis Kudriashov >> wrote: >> >>> >>> >>> 2017-08-16 12:02 GMT+02:00

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

2017-08-16 12:28 GMT+02:00 Guillermo Polito : > > > On Wed, Aug 16, 2017 at 12:13 PM, Denis Kudriashov > wrote: > >> >> >> 2017-08-16 12:02 GMT+02:00 Guillermo Polito : >> >>> >>> >>> On Wed, Aug 16, 2017 at 10:50 AM,

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Wed, Aug 16, 2017 at 12:13 PM, Denis Kudriashov wrote: > > > 2017-08-16 12:02 GMT+02:00 Guillermo Polito : > >> >> >> On Wed, Aug 16, 2017 at 10:50 AM, Denis Kudriashov >> wrote: >> >>> There is possibility where delay

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

2017-08-16 12:02 GMT+02:00 Guillermo Polito : > > > On Wed, Aug 16, 2017 at 10:50 AM, Denis Kudriashov > wrote: > >> There is possibility where delay can be used during startup/shutdown. >> Library can clean resources which are managed by kind of

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Wed, Aug 16, 2017 at 10:50 AM, Denis Kudriashov wrote: > There is possibility where delay can be used during startup/shutdown. > Library can clean resources which are managed by kind of pool which > organizes timeout logic to enter synchronization monitor. > > I checked

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

There is possibility where delay can be used during startup/shutdown. Library can clean resources which are managed by kind of pool which organizes timeout logic to enter synchronization monitor. I checked Seamless which manages connections this way. But I not found any issue there. 2017-08-16

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Tue, Aug 15, 2017 at 3:25 PM, Ben Coman wrote: > In case any of the shutdown/startup scripts use a delay, now or in the > future, > I'd first try athighestPriority-1 to avoid influence on the > DelayScheduler. > but then Eliot's suggestion to valueUnpreemptively may

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

Hi Ben, > On Aug 15, 2017, at 6:25 AM, Ben Coman wrote: > > In case any of the shutdown/startup scripts use a delay, now or in the > future, > I'd first try athighestPriority-1 to avoid influence on the > DelayScheduler. +1. In fact I'd raise it to no more than

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

In case any of the shutdown/startup scripts use a delay, now or in the future, I'd first try athighestPriority-1 to avoid influence on the DelayScheduler. but then Eliot's suggestion to valueUnpreemptively may avoid that anyway. btw, what happens if an error occurs inside valueUnpreemptively?

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

Thanks for this discussion! It will improve Guille proposal and Pharo :) I'm happy! And learning things. (ok I should prepare my lectures instead of reading. I guess that I will have to use pomodoro techniques to force me to work :) Stef On Mon, Aug 14, 2017 at 9:48 PM, Eliot Miranda

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Mon, Aug 14, 2017 at 12:26 PM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi Eliot, > > On Mon, Aug 14, 2017 at 9:07 PM, Eliot Miranda > wrote: > >> Hi Guille, >> >> On Mon, Aug 14, 2017 at 3:42 AM, Guillermo Polito < >> guillermopol...@gmail.com> wrote:

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

Hi Eliot, On Mon, Aug 14, 2017 at 9:07 PM, Eliot Miranda wrote: > Hi Guille, > > On Mon, Aug 14, 2017 at 3:42 AM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> Hi all, >> >> I'm proposing a kind-of critical change that I believe is very good for >> the

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

Hi Guille, On Mon, Aug 14, 2017 at 3:42 AM, Guillermo Polito wrote: > Hi all, > > I'm proposing a kind-of critical change that I believe is very good for > the health of the system: I want that the startup of the system runs in > maximum priority and becomes

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

On Mon, Aug 14, 2017 at 4:47 PM, Tim Mackinnon wrote: > I’m definitely in favour of doing something (as I found it confusing, and > in a way also found it has the potential to leak what could be sensitive > information through command line contexts that are still lurking in the

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

Hi guille thanks for raising this point. I will wait a bit that other people comment on it since it is a crucial point. Stef On Mon, Aug 14, 2017 at 4:47 PM, Tim Mackinnon wrote: > I’m definitely in favour of doing something (as I found it confusing, and > in a way also

Re: [Pharo-dev] Issue 20309 - Startup should run always in a fresh process

I’m definitely in favour of doing something (as I found it confusing, and in a way also found it has the potential to leak what could be sensitive information through command line contexts that are still lurking in the image with details about previous directory structures and commands). I

[Pharo-dev] Issue 20309 - Startup should run always in a fresh process

Hi all, I'm proposing a kind-of critical change that I believe is very good for the health of the system: I want that the startup of the system runs in maximum priority and becomes non-interruptable. Right now, when you save your image, the shutdown and startup are run in the same priority than