On Fri, Jun 02, 2023 at 01:21:15PM +0200, tlaro...@polynum.com wrote:
> > I have not read most of the traffic yet, but I feel, fairly strongly,
> > that inetd should _not_ exit, except (maybe) if the config is broken
> > during its initial startup. It's a critical service.
>
> So I will put t
On Sun, Jun 04, 2023 at 07:20:05AM +1000, Luke Mewburn wrote:
> Does anything in-tree use libarchive's mtree implementation?
tar?
Joerg
>> Rhialto pointed me to sysexits(3) that was exactly what I was
>> looking for (for inetd(8) revision). So kudos to him!
> I deliberately didn't mention sysexits.h (or sysexits(3)) as I don't
> think it is really appropriate here.
I agree and I disagree.
I agree that it certainly isn't the same
On 23-06-01 15:44, Valery Ushakov wrote:
| We have mtree(8) man page for our mtree that documents the format of
| the mtree spec. We also have an mtree(5) page that documents the
| format of the mtree spec, but that pages comes from libarchive. This
| is kinda confusing.
I agree!
| W
Le Sat, Jun 03, 2023 at 11:28:31PM +0700, Robert Elz a écrit :
> Date:Sat, 3 Jun 2023 13:45:44 +0200
> From:tlaro...@polynum.com
> Message-ID:
>
> | Rhialto pointed me to sysexits(3) that was exactly what I was looking
> | for (for inetd(8) revision). So kudos to
Date:Sat, 3 Jun 2023 13:45:44 +0200
From:tlaro...@polynum.com
Message-ID:
| Rhialto pointed me to sysexits(3) that was exactly what I was looking
| for (for inetd(8) revision). So kudos to him!
I deliberately didn't mention sysexits.h (or sysexits(3)) as I don't
> Date: Sat, 3 Jun 2023 14:12:21 +0200
> From: tlaro...@polynum.com
>
> Le Sat, Jun 03, 2023 at 12:02:20PM +, Taylor R Campbell a écrit :
> > > Date: Sat, 3 Jun 2023 13:45:44 +0200
> > > From: tlaro...@polynum.com
> > >
> > > So I suggest to add a mention of sysexits(7) to style.
> >
> > I d
Le Sat, Jun 03, 2023 at 12:25:01PM +, Taylor R Campbell a écrit :
> > Date: Sat, 3 Jun 2023 14:12:21 +0200
> > From: tlaro...@polynum.com
> >
> > Le Sat, Jun 03, 2023 at 12:02:20PM +, Taylor R Campbell a écrit :
> > > > Date: Sat, 3 Jun 2023 13:45:44 +0200
> > > > From: tlaro...@polynum.co
Le Sat, Jun 03, 2023 at 12:02:20PM +, Taylor R Campbell a écrit :
> > Date: Sat, 3 Jun 2023 13:45:44 +0200
> > From: tlaro...@polynum.com
> >
> > So I suggest to add a mention of sysexits(7) to style.
>
> I don't think sysexits(7) is consistently used enough, or really
> useful enough, to war
Le Sat, Jun 03, 2023 at 02:01:50PM +0200, Martin Husemann a écrit :
> On Sat, Jun 03, 2023 at 01:45:44PM +0200, tlaro...@polynum.com wrote:
> > Furthermore, I'm adding a RETURN VALUES section to inetd.8 and I think
> > it should be standard practice for sys programs.
>
> That is for functions retu
> Date: Sat, 3 Jun 2023 13:45:44 +0200
> From: tlaro...@polynum.com
>
> So I suggest to add a mention of sysexits(7) to style.
I don't think sysexits(7) is consistently used enough, or really
useful enough, to warrant being a part of the style guide. Very few
programs, even those in src, use it,
On Sat, Jun 03, 2023 at 01:45:44PM +0200, tlaro...@polynum.com wrote:
> Furthermore, I'm adding a RETURN VALUES section to inetd.8 and I think
> it should be standard practice for sys programs.
That is for functions returning a value, the proper .Sh here would
be EXIT STATUS.
Martin
Rhialto pointed me to sysexits(3) that was exactly what I was looking
for (for inetd(8) revision). So kudos to him!
I'm converting inetd(8) to exiting with conventional values defined
in sysexits(3) since:
- it auto-documents the code;
- it allows to script in a consistent manner t
13 matches
Mail list logo
