| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
https://cvsweb.openbsd.org/src/lib/libc/stdio/vfprintf.c?rev=1.79&content-type=text/x-cvsweb-markup
I think this is silly, as I've said elsewhere, and it's a shame
because that was clearly the best way to write this. Oh well.
|
| |
|
|
|
| |
It's a little annoying to have to special-case this, but otherwise there
is no confirmation in the log that the restart won't still happen.
|
| |
|
|
|
| |
The intervals are configurable in milliseconds so humanize should be
able to display at that precision.
|
| | |
|
| | |
|
| |
|
|
| |
Unlikely to happen since ARG_MAX is 256K, but...
|
| | |
|
| |
|
|
| |
setgroups fails when already running as a user.
|
| |
|
|
|
|
| |
This allows running things like kfcgi which do their own privilege
dropping and chrooting. Need to update the examples with something like
that.
|
| | |
|
| |
|
|
| |
This lets us properly signal services with child processes of their own.
|
| |
|
|
|
|
|
|
|
| |
> If a command is not found, the exit status shall be 127. If the
> command name is found, but it is not an executable utility, the exit
> status shall be 126. Applications that invoke utilities without using
> the shell should use these exit status values to report similar errors.
[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_02
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
These are the two priorities that go to a normal place
(/var/log/messages) by default.
|
| | |
|
| |
|
|
|
| |
It's unclear whether closelog is really safe to call in pre-exec
context, so just trust that the log is opened with CLOEXEC.
|
| | |
|
| |
|
|
|
| |
Changed line reading functions to return const char * because modifying
the strings by adding '\0' into them screws up the following call.
|
| |
|
|
| |
CLOCK_MONOTONIC exists everywhere.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|