Re: [CODE] inetd FINAL

Le Mon, Jul 03, 2023 at 08:23:13PM +0100, David Brownlee a écrit : > Some random thoughts :) > > - Would it make sense to actively reject -l or similar when -c is given I don't think so. They can be a "slip of the thumb" when passing switches and they do no harm---the problem is that the checking

Re: [CODE] inetd FINAL

Some random thoughts :) - Would it make sense to actively reject -l or similar when -c is given - Resilient mode would probably benefit from a new {sub ,}section heading in the man page - I'd be inclined to reject a config which tries to embed a null with \000 or similar with an error David

[CODE] inetd FINAL

Here is the final code with all implemented: http://downloads.kergis.com/misc/inetd.tar.gz The new version: $ ls -l ./inetd -rwxr-xr-x 1 alceste wheel 76136 Jul 3 19:55 ./inetd $ size ./inetd textdata bss dec hex filename 563073008 11016 70331 112bb ./inetd v

[CODE] inetd OK

The new version passes the tests for current ATF, and does what was proposed. I have corrected two blunders: - wrong macro: the debug flag (in the usage and in support) was conditionnally added with: #define DEBUG #else #endif when the macro is DEBUG_ENABLE... - the program writes via syslog o

[CODE] inetd(8)

You will find here: http://downloads.kergis.com/misc/inetd.tar.gz the sources for implementation of what I had proposed for inetd(8): - Create a checker mode; - Never serve a not valid config; - Resilient mode; - Fallback feature; - Restate the syntax (there are extensions to bypass things I fin

Re: [CODE] inetd

Le Mon, Jun 19, 2023 at 07:34:43PM +0200, tlaro...@polynum.com a écrit : > The new version of inetd is here: > > http://downloads.kergis.com/misc/inetd.tar.gz > > I have rewritten the majority of the parsing code, and put everything > in parse.c, with a lot of comments---there is no more parse_v2

[CODE] inetd

The new version of inetd is here: http://downloads.kergis.com/misc/inetd.tar.gz I have rewritten the majority of the parsing code, and put everything in parse.c, with a lot of comments---there is no more parse_v2.c since with two different files, for the same thing, things were not parsed exactly

[CODE] inetd

For the ones who want to look at it, the current state of my work is here: http://downloads.kergis.com/misc/inetd.tar.gz You will at least see that I have rewritten a lot of parse.c and parse_v2.c (and will in fact rewrite almost everything about the parsing), inetd.c being the legacy and "easy"