supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Paul Sopka <psopka@sopka.ch>
To: Peter Pentchev <roam@ringlet.net>, supervision@list.skarnet.org
Subject: Re: s6/s6-rc policy for Gentoo: user session tracking
Date: Sat, 13 Jul 2024 12:22:04 +0200	[thread overview]
Message-ID: <6a9692b4-5d64-4374-b545-d90e6c9d35e9@sopka.ch> (raw)
In-Reply-To: <ZpJMM3izRR17mSYe@straylight.m.ringlet.net>


[-- Attachment #1.1.1: Type: text/plain, Size: 810 bytes --]

> These two last points, if you really decide to implement them like that in
> the final version, may require some synchronization, e.g. via file locking.
> It is not impossible (I mean, it is quite unlikely, but especially with
> automated CI systems not impossible *at all*) for two SSH sessions to
> come in practically at once, and I have indeed seen shell startup scripts
> run the same program at the same time.
Good point. If I understood everything correctly, this can be easily 
solved by the "flock" command, right?

> It would be... interesting to have one login session write the first line,
> then another session immediately write the second one, and then neither of
> them will find exactly one line in the file 🙂 And same for logout.
Indeed.


Have a nice weekend!

Paul


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3195 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-07-14  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 14:53 Paul Sopka
2024-07-13  9:43 ` Peter Pentchev
2024-07-13 10:22   ` Paul Sopka [this message]
2024-07-14 11:41     ` Laurent Bercot
2024-07-14 21:00       ` Paul Sopka
2024-07-15 15:34         ` Laurent Bercot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a9692b4-5d64-4374-b545-d90e6c9d35e9@sopka.ch \
    --to=psopka@sopka.ch \
    --cc=roam@ringlet.net \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).