[1]
Damn ezmlm-cgi bug, this time it triggered without an accented
character. Sorry about that :(
Here's the URL to the full message:
https://www.mail-archive.com/supervision@list.skarnet.org/msg01427.html
About customizing shutdown signals in s6-rc: how do you suggest it
should
be done?
Nevertheless, s6-svwait -o seems to also fail if some failure occurs
before the wanted state is reached, eg. one `dnscrypt-proxy' instance
reporting permanent failure before another one comes up successfully.
So we might need to add an option to ignore such failures.
Yes, that's a good point. I
May 2, 2017 12:08 AM, "Alex Efros" wrote:
> Hi!
Hey! First of all, thanks for the quick, polite reply. Didn't expect to be
written in days, actually - so that on itself is already a good-enough greeting.
> That sounds like everyone has own preference and that's ok. If you
> like complexity and
What I would like to have is "s6-rc -d change foo" sending SIGTERM and then
SIGKILL if the service is not down after x seconds. Currently If a daemon hangs
it has annoying side effects. If I don't put a timeout on the s6-rc command
the state machine is blocked, and I cannot shut down the system any
May 2, 2017 8:35 AM, "Steve Litt" wrote:
> I also am surprised you could get Gnome to work without systemd. Just
> for fun, try out LXDE, and install dmenu and have it at the ready
> with an easy hotkey. I think you'll love the productivity
> enhancement, once you get used to it.
Yes, GNOME wor
"It's old software. Its last version is from 2014."
Old? Let's see...
The MTA used by this very mailing-list is netqmail-1.06, i.e.
qmail (latest version released in 1996) with user-contributed patches,
the latest of which is from 2005.
So yeah, that's 12 years old software. It could be g
On Tue, May 02, 2017 at 09:34:52AM +, Laurent Bercot wrote:
> systemd, on the other hand, hasn't left the maternity hospital - but
> how could it? it's such a fragile baby, it needs constant attention,
> it can barely leave the incubator. If you ask me, it should never have
> left the womb in
What I would like to have is "s6-rc -d change foo" sending SIGTERM and
then
SIGKILL if the service is not down after x seconds. Currently If a
daemon hangs
it has annoying side effects. If I don't put a timeout on the s6-rc
command
the state machine is blocked, and I cannot shut down the system
Yes, I think this is the correct behaviour: if the user does not want
it, the warnings can be somehow filtered; on the other hand, there would
not be a trivial way to know such failures if the user wants it but
there is no warning in the first place.
By the way, if this change is done in s6-svwait
On Tue, May 02, 2017 at 08:51:19AM +, Laurent Bercot wrote:
> If I were to work on a more official, better integrated solution, I would
> do it at the s6-supervise level. I would not implement custom control
> scripts, for the reasons indicated in the above link, but it would
> probably be po
* Casper Ti. Vector [20170502 12:48]:
> On Tue, May 02, 2017 at 08:51:19AM +, Laurent Bercot wrote:
> > If I were to work on a more official, better integrated solution, I would
> > do it at the s6-supervise level. I would not implement custom control
> > scripts, for
> Doesn't
>
>svc -wD -T1000 servicedir || svc -k servicedir
>
> do what you want for the "hangup problem" ?
Problem is that you can't trigger that from s6-rc.
Lionel
By the way, if this change is done in s6-svwait, perhaps the s6-rc FAQ
can mention that dynamic (i.e. without using s6-rc-update manually)
virtual dependencies can be implemented using s6-svwait oneshots?
Probably not. If anything, I'll think about the use of s6-svwait
oneshots
a bit more, and
That would be much cleaner. Thanks :)
On Tue, May 02, 2017 at 02:40:56PM +, Laurent Bercot wrote:
> Probably not. If anything, I'll think about the use of s6-svwait > oneshots
> a bit more, and if I assess it's the correct, or as correct as it gets,
> way to implement disjunctions, I'll add
May 2, 2017 12:00 PM, "Laurent Bercot"
wrote:
> Old? Let's see...
> The MTA used by this very mailing-list is netqmail-1.06, i.e.
> qmail (latest version released in 1996) with user-contributed
> patches, the latest of which is from 2005.
> So yeah, that's 12 years old software. It could be going
Well, I found this to be fairly over-simplified. If all members of the
disjunction are longruns, using s6-svwait is OK; however this is not
directly extensible to oneshots and bundles. Nevertheless, I think the
idea of using a separate command to wait for the disjunction is still
architecturally
Laurent Bercot:
> > "It's old software. Its last version is from 2014."
>
> Old? Let's see...
A more amusant counterexample is perhaps the Debian Almquist shell, put into
widespread use on Debian and Ubuntu a decade ago in order to speed up bootstrap.
M. Almquist first published it in May 1989.
Hi!
On Tue, May 02, 2017 at 07:16:24PM +0200, Francisco Gómez wrote:
> Besides, if you could magically do perfect small
> applications, that means you'd have to keep working with and on
> millions of small tools, right? Wouldn't that just add up complexity!?
It depends, but in general just having
Laurent Bercot:
> It is also true that it would benefit from closer maintenance.
> Gerrit Pape, runit's author, is still around and still reads this list,
> but is not as active as he was a few years ago (typically during
> runit development). Fortunately, there are not many feature requests.
Laurent Bercot:
> Lots of work have been put into s6 in the last few years, more than in any
> other supervision suite, with the possible exception of nosh;
(-:
Laurent Bercot:
> the fact that Void Linux has not yet switched to s6 is proof that runit is
> still working well enough for them and th
The Debian maintainer is now Dmitry Bogatov.
* https://tracker.debian.org/pkg/runit
And unless I'm mistaken, he's not subscribed to this list, which is
a shame. It makes no sense for software to only be maintained for a
distribution (unless, of course, it's distribution-specific software);
and
Francisco Gómez García:
> And the person who told me the "it is too old" thing used arguments
> such as "it will eventually not compile" - while I doubt a small codebase
> on plain C will stop compiling in the near future, it is indeed something
> to keep an eye on.
That person needs to learn f
Hi,
2017-05-02 6:32 GMT-03:00 Francisco Gómez García:
>
> May 2, 2017 8:35 AM, "Steve Litt" wrote:
>
>> I also am surprised you could get Gnome to work without systemd. Just
>> for fun, try out LXDE, and install dmenu and have it at the ready
>> with an easy hotkey. I think you'll love the product
On Mon, 01 May 2017 23:11:25 +0200
Francisco Gómez wrote:
> "It's old software. Its last version is from 2014. If I have to
> choose between a dynamic, bug-filled init like Systemd and a barely
> maintained init like Runit, I'd rather use Systemd."
>
> That sounds bad, doesn't it?
Y
24 matches
Mail list logo