On Mon, 2019-07-15 at 00:00 +0200, Martin Steigerwald wrote:
> Hello.
>
> Theodore Ts'o - 14.07.19, 22:07:
> > So requiring support of non-systemd ecosystems is in general, going to
> > require extra testing. In the case of cron/systemd.timers, this
> > means testing and/or careful code inspectio
Peter Pentchev writes:
> On Sun, Jul 14, 2019 at 12:30:16PM -0700, Russ Allbery wrote:
>> There seems to be a clear infrastructure gap for the non-systemd world
>> here that's crying out for some inetd-style program that implements the
>> equivalent of systemd socket activation and socket passing
Hi,
On Mon, Jul 15, 2019 at 01:49:04PM +0200, Guillem Jover wrote:
> > In the same way, we could implement "service monitoring" in sysvinit by
> > adding an "inittab.d" directory, but I'm fairly sure that I'm not the first
> > person who had this idea in the last thirty years, so there is probabl
On Mon, Jul 15, 2019 at 6:48 PM Simon Richter wrote:
> The main limitation seems to be that it's not permitted to modify
> inetd.conf from maintainer scripts. We could probably "fix" this by adding
> an "inetd.conf.d" mechanism.
There is update-inetd, but it doesn't support xinetd and doesn't
app
On Mon, 2019-07-15 at 12:30:09 +0200, Simon Richter wrote:
> On Sun, Jul 14, 2019 at 07:23:31PM +0100, Simon McVittie wrote:
> > Some systemd system services are meant to start on-demand via socket
> > events (systemd.socket(5)), and can work via inetd on non-systemd-booted
> > systems. micro-httpd
On Sun, Jul 14, 2019 at 12:30:16PM -0700, Russ Allbery wrote:
> Vincent Bernat writes:
>
> > inetd uses stdin/stdout to communicate with the daemon and have to
> > launch one instance for each client connecting. systemd.socket pass a
> > regular listening socket on first connection to the daemon
Hi,
On Sun, Jul 14, 2019 at 07:23:31PM +0100, Simon McVittie wrote:
> Some systemd system services are meant to start on-demand via socket
> events (systemd.socket(5)), and can work via inetd on non-systemd-booted
> systems. micro-httpd appears to be an example of this - I'm a bit surprised
> the
Vincent Bernat writes:
> ❦ 14 juillet 2019 12:30 -07, Russ Allbery :
>> There seems to be a clear infrastructure gap for the non-systemd world
>> here that's crying out for some inetd-style program that implements the
>> equivalent of systemd socket activation and socket passing using the
>> sam
Hello.
Theodore Ts'o - 14.07.19, 22:07:
> So requiring support of non-systemd ecosystems is in general, going to
> require extra testing. In the case of cron/systemd.timers, this
> means testing and/or careful code inspection to make sure the
> following cases work:
>
> * systemd && cron
❦ 14 juillet 2019 12:30 -07, Russ Allbery :
> There seems to be a clear infrastructure gap for the non-systemd world
> here that's crying out for some inetd-style program that implements the
> equivalent of systemd socket activation and socket passing using the same
> protocol, so that upstreams
On Sun, Jul 14, 2019 at 07:23:31PM +0100, Simon McVittie wrote:
> micro-httpd appears to be an example of this - I'm a bit surprised
> there aren't more. Perhaps this indicates limitations in the infrastructure
> around inetd services making it hard to implement "use systemd.socket(5)
> under syste
Vincent Bernat writes:
> inetd uses stdin/stdout to communicate with the daemon and have to
> launch one instance for each client connecting. systemd.socket pass a
> regular listening socket on first connection to the daemon and the
> daemon can then serve multiple clients.
I believe the wait op
❦ 14 juillet 2019 19:23 +01, Simon McVittie :
> Some systemd system services are meant to start on-demand via socket
> events (systemd.socket(5)), and can work via inetd on non-systemd-booted
> systems. micro-httpd appears to be an example of this - I'm a bit surprised
> there aren't more. Perhap
; by one of the targets that are reached during boot,
but the converse is not true. Not every systemd service is "required"
or "wanted" by those targets: some systemd services start on-demand,
which is not a concept that exists within the narrower scope of LSB
init scripts.
On Friday 04 May 2007 05:53:39 Marc Haber wrote:
> >I think that would give you the best of both worlds, particularly if
> > it's combined with logging so that the *full* output, without any
> >prettification, goes into a file on disk somewhere.
>
> Agreed, with the option of having the whole blurb
In Thu, 03 May 2007 13:39:32 -0700, Russ Allbery <[EMAIL PROTECTED]>
wrote:
>I think that would give you the best of both worlds, particularly if it's
>combined with logging so that the *full* output, without any
>prettification, goes into a file on disk somewhere.
Agreed, with the option of havin
On Thu, 03 May 2007 18:13:25 -0700
Russ Allbery <[EMAIL PROTECTED]> wrote:
> Lars Wirzenius <[EMAIL PROTECTED]> writes:
> > On to, 2007-05-03 at 13:39 -0700, Russ Allbery wrote:
>
> >> My ideal output format would just list "subsystem OK"
>
> > While we're daydreaming, I'd like an empty screen w
Lars Wirzenius <[EMAIL PROTECTED]> writes:
> On to, 2007-05-03 at 13:39 -0700, Russ Allbery wrote:
>> My ideal output format would just list "subsystem OK"
> While we're daydreaming, I'd like an empty screen with a timer counting
> down how long (in seconds) I have until I can actually use the ma
On to, 2007-05-03 at 13:39 -0700, Russ Allbery wrote:
> My ideal output format would just list "subsystem OK"
While we're daydreaming, I'd like an empty screen with a timer counting
down how long (in seconds) I have until I can actually use the machine.
Unless there's a problem, of course, in whic
Lennart Sorensen <[EMAIL PROTECTED]> writes:
> On Thu, May 03, 2007 at 10:08:20PM +0200, Marc Haber wrote:
>> This is also a "sales" issue. I have seen to many faces darken when
>> people see a Debian system boot for the first time. People get reminded
>> of the old DOS days and decide that this L
On Thu, May 03, 2007 at 10:08:20PM +0200, Marc Haber wrote:
> This is also a "sales" issue. I have seen to many faces darken when
> people see a Debian system boot for the first time. People get
> reminded of the old DOS days and decide that this Linux thing is too
> ugly to use.
So knowledge is u
ll. I do not feel very comfortable with
using the interface yet. I have only migrated two packages, exim4 and
nagios2, to LSB init scripts, and for both packages I needed a generic
log function which was kindly contributed by madduck on IRC:
|# this is from madduck on IRC, 2006-07-06
|# There s
also sprach Thomas Viehmann <[EMAIL PROTECTED]> [2006.06.02.0847 +0200]:
> Would combining the drives that went well make sense?
> Starting RAID devices... md0, md1, md4 done
> Starting RAID device md2 ... 2/3 drives, degraded
> Starting RAID device md3 ... 1/3 drives, failed
Nice, but is it wort
On Fri, Jun 02, 2006 at 02:36:15AM -0400, Joey Hess wrote:
> Adam Borowski wrote:
> > The friend muttered something about Ubuntu being as flaky as
> > Windows, then rebooted and started the installation anew...
>
> This is not an Ubuntu mailing list. It's pretty annoying to require all
> us d-
martin f krafft wrote:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2006.06.01.2122 +0200]:
>>> Starting RAID device md0 ... 3 drives, done
>>> Starting RAID device md1 ... 3 drives, done
>>> Starting RAID device md2 ... 2/3 drives, degraded
>>> Starting RAID device md3 ... 1/3 drives, failed
Adam Borowski wrote:
> The friend muttered something about Ubuntu being as flaky as
> Windows, then rebooted and started the installation anew...
This is not an Ubuntu mailing list. It's pretty annoying to require all
us d-i developers to get this far down in the mail before we realize
that th
On Fri, Jun 02, 2006 at 02:44:54AM +0200, martin f krafft wrote:
> also sprach Matthew R. Dempsky <[EMAIL PROTECTED]> [2006.06.02.0238 +0200]:
> > > Any suggestions?
> >
> > Submit a feature request to LSB?
>
> And wait 15 years?
Eh, that's only 2 or 3 debian releases from now.
--
To UNSUBSCR
also sprach Matthew R. Dempsky <[EMAIL PROTECTED]> [2006.06.02.0238 +0200]:
> > Any suggestions?
>
> Submit a feature request to LSB?
And wait 15 years?
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian de
On Thu, Jun 01, 2006 at 06:51:31PM +0200, martin f krafft wrote:
> Any suggestions?
Submit a feature request to LSB?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
also sprach Arjan Oosting <[EMAIL PROTECTED]> [2006.06.01.2307 +0200]:
> It would be nice if the log_action_end_msg would support warnings
> in addition to succes and failures, so the output would clearly
> distinguish a degraded array from a completely succesfully started
> array.
Consider filing
Op do, 01-06-2006 te 22:29 +0200, schreef martin f krafft:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2006.06.01.2150 +0200]:
> > Stopping RAID devices... md6 busy; md5 busy; md3 busy; md2 busy; md0
> > busy; md1 busy; failed (6 busy, 1 stopped).
> > Starting RAID devices... md0 running; md
On Thu, Jun 01, 2006 at 06:51:54PM +0200, martin f krafft wrote:
> In my ideal world, this is what it would look like:
>
> Starting RAID devices ...
> /dev/md0 has been started with 3 drives.
> /dev/md1 has been started with 3 drives.
> /dev/md2 assembled from 2 drives - need all 3 to start
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.06.01.2150 +0200]:
> Stopping RAID devices... md6 busy; md5 busy; md3 busy; md2 busy; md0
> busy; md1 busy; failed (6 busy, 1 stopped).
> Starting RAID devices... md0 running; md1 running; md2 running; md3
> running; md4 started (3/3); md5 runni
also sprach Ron Johnson <[EMAIL PROTECTED]> [2006.06.01.2158 +0200]:
> Starting them individually just seems "better" IMO, more atomic.
Mh, I would have to do config file parsing in the init.d script to
figure out all available devices. mdadm already handles it; it
starts all devices that haven't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
martin f krafft wrote:
> also sprach Daniel Jacobowitz <[EMAIL PROTECTED]> [2006.06.01.2012 +0200]:
>> Starting RAID device md0 ... 3 drives, done
>> Starting RAID device md1 ... 3 drives, done
>> Starting RAID device md2 ... 2/3 drives, degraded
>> St
also sprach martin f krafft <[EMAIL PROTECTED]> [2006.06.01.2122 +0200]:
> > Starting RAID device md0 ... 3 drives, done
> > Starting RAID device md1 ... 3 drives, done
> > Starting RAID device md2 ... 2/3 drives, degraded
> > Starting RAID device md3 ... 1/3 drives, failed
> > Starting RAID device
also sprach Daniel Jacobowitz <[EMAIL PROTECTED]> [2006.06.01.2012 +0200]:
> Starting RAID device md0 ... 3 drives, done
> Starting RAID device md1 ... 3 drives, done
> Starting RAID device md2 ... 2/3 drives, degraded
> Starting RAID device md3 ... 1/3 drives, failed
> Starting RAID device md4 ...
On Thu, Jun 01, 2006 at 06:51:54PM +0200, martin f krafft wrote:
> In my ideal world, this is what it would look like:
>
> Starting RAID devices ...
> /dev/md0 has been started with 3 drives.
> /dev/md1 has been started with 3 drives.
> /dev/md2 assembled from 2 drives - need all 3 to start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
martin f krafft wrote:
> > also sprach Andreas Fester <[EMAIL PROTECTED]> [2006.06.01.1935 +0200]:
>> >> log_action_msg "Starting RAID devices ..."
> >
> > log_action_msg is supposed to be used to log an atomic message,
> > which is not the case the wa
also sprach Andreas Fester <[EMAIL PROTECTED]> [2006.06.01.1935 +0200]:
> log_action_msg "Starting RAID devices ..."
log_action_msg is supposed to be used to log an atomic message,
which is not the case the way we/you use it here.
> log_failure_msg "... done assembling RAID devices: failed."
Acc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
martin f krafft wrote:
> I am faced with the problem on how to tackle multiline output from
> an init.d script, which I have just converted to LSB. Since the
> package is mdadm and RAID is kinda essential to those that have it
> configured, I'd rather
On 6/1/06, martin f krafft <[EMAIL PROTECTED]> wrote:
Hi,
I am faced with the problem on how to tackle multiline output from
an init.d script, which I have just converted to LSB. Since the
package is mdadm and RAID is kinda essential to those that have it
configured, I'd rather not hide informat
Hi,
I am faced with the problem on how to tackle multiline output from
an init.d script, which I have just converted to LSB. Since the
package is mdadm and RAID is kinda essential to those that have it
configured, I'd rather not hide information but give the user the
entire process.
In my ideal w
43 matches
Mail list logo
