auto-logout

[PAUL DEBRUICKER]

Does tODE have a setting to auto log out a session when a command hasn't been run in e.g. and hour ?

[Dale Henrichs]

No I don't have anything like that in tODE ... It might be difficult to know when nothing has happened for an hour, since the console is not ... 

Are you worried about commit record backlog?

Dale

On Wed, Mar 23, 2022 at 11:27 AM PAUL DEBRUICKER <pdeb...@gmail.com> wrote:

Does tODE have a setting to auto log out a session when a command hasn't been run in e.g. and hour ?

--
You received this message because you are subscribed to the Google Groups "tODE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tode_st+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tode_st/7AA237A1-EA0C-4E3C-B228-836B93A26987%40gmail.com.

[PAUL DEBRUICKER]

Yep I keep forgetting to log out consistently so come back to bloated stones. Which are easy enough to shrink but would rather not risk running out of space because I'm forgetful.

> To view this discussion on the web visit https://groups.google.com/d/msgid/tode_st/CAFuPq9WV4h1C-L0u%3Dq06WvXOxvftVhoq7awuZV-dnbySdbtbNg%40mail.gmail.com.

[Dale Henrichs]

Ah …. for commit record backlogs it should be possible possible to set up a sigabort handler … I’ve been in an all day meeting today and again tomorrow but I should be able to find time over the weekend to put a script together …

Dale

Sent from my iPhone

> On Mar 24, 2022, at 9:36 AM, PAUL DEBRUICKER <pdeb...@gmail.com> wrote:
>
> Yep I keep forgetting to log out consistently so come back to bloated stones. Which are easy enough to shrink but would rather not risk running out of space because I'm forgetful.

> To view this discussion on the web visit https://groups.google.com/d/msgid/tode_st/FBE7E757-B45A-4838-8970-6C4C6702FD70%40gmail.com.

[Dale Henrichs]

Paul,

I spent a little bit of time today, seeing if I could write a tODE script that would handle SIGABORT and while I can write the smalltalk code, for a "keepalive" script, terminating the script is bit awkward (hard break is the only option to interrupt a script ... and I can't do anything intelligent in Smalltalk to handle a  hard break) ... the next option would be to create a builtin client-side command, where we could arrange to handle SIGABORTs in the Pharo client, but to do that cleanly we'd have to arrange to have a transaction mutex so that in the event you are explicitly running a long running process, the SIGABORT  process can be prevented from doing an abort at an inopportune time :) ...

My "keepalive" script was going to be something that you would either run before leaving the idle session, or tack onto a long running command line, that would run AFTER the long running process finished (the use case I assume you are most interested in) ... I think that the "keepalive" script I've written would fill the bill, but you'd have to manually run a "cleanupAfterKeepalive" script ... If you would find that useful, I could arrange to write the cleanup script and give you the keepalive script :) 

Dale