On Sat, Nov 07, 2020 at 12:48:11PM +0100, Martin Vahlensieck wrote:
> Hi
>
> Unbound on OpenBSD does not have a pidfile, so remove the reference in
> the manual. As the variable is empty, it also incorrectly formats the
> description as italic.
>
> Best,
>
> Ma
Hi
Unbound on OpenBSD does not have a pidfile, so remove the reference in
the manual. As the variable is empty, it also incorrectly formats the
description as italic.
Best,
Martin
Index: unbound.conf.5.in
===
RCS file: /cvs/src
IL Ka wrote:
> >
> > pid files can easily get out of sync with the expected process (example:
> > daemon starts, writes a pid file, later it crashes. at any point between
> > the crash and you trying to stop/restart the daemon another process
> > could be assigned the same pid, then the wrong pro
>
> pid files can easily get out of sync with the expected process (example:
> daemon starts, writes a pid file, later it crashes. at any point between
> the crash and you trying to stop/restart the daemon another process
> could be assigned the same pid, then the wrong process is signalled).
>
Wo
On 2018/06/02 23:07, Il Ka wrote:
> rc.subr(8) uses pgrep(1)/pkill(1) to control daemons
> using their command lines.
This is intentional.
pid files can easily get out of sync with the expected process (example:
daemon starts, writes a pid file, later it crashes. at any point between
the crash an
able to
produce pidfile, but lacks of tool to control it.
So, I added ``daemon_pidfile`` variable to rc.subr(8).
If this variable is not set then everything works as usual.
But if you set it then system uses it to check (ps -p),
stop and reload (kill) daemon.
I then simply tell gunicorn to write
On Tue, Oct 27, 2015 at 02:28:51PM +0100, Jan Stary wrote:
> > usr.sbin/rbootd: rbootd.c
> > usr.sbin/rarpd : rarpd.c
> > usr.sbin/mrouted: main.c
> > usr.bin/usbhidaction: usbhidaction.c
> > usr.sbin/wsmoused: wsmoused.8 wsmoused.c wsmoused.h
> > usr.sbin/ypserv/ypserv
d cron have already had the pidfile removed.
Below is a diff for lpd.
- todd
Index: usr.sbin/lpr/SMM.doc/7.t
===
RCS file: /cvs/src/usr.sbin/lpr/SMM.doc/7.t,v
retrieving revision 1.5
diff -u -p -u -r1.5 7.t
--- usr.sbin/lpr/SMM.doc/7.t
> usr.sbin/rbootd: rbootd.c
> usr.sbin/rarpd : rarpd.c
> usr.sbin/mrouted: main.c
> usr.bin/usbhidaction: usbhidaction.c
> usr.sbin/wsmoused: wsmoused.8 wsmoused.c wsmoused.h
> usr.sbin/ypserv/ypserv: Makefile ypserv.c
> usr.sbin/pppd : main.c
Belo
ok!
J??r??mie Courr??ges-Anglas(j...@wxcvbn.org) on 2015.10.25 23:15:12 +0100:
>
> Following the recent discussions, here's another pidfile(3) removal.
> route6d(8) doesn't document it.
>
> ok?
>
> Index: Makefile
>
Following the recent discussions, here's another pidfile(3) removal.
route6d(8) doesn't document it.
ok?
Index: Makefile
===
RCS file: /cvs/src/usr.sbin/route6d/Makefile,v
retrieving revision 1.7
diff -u -p -r1.
L_FORWARDING in base, so IMO it doesn't call for a change
> in kern_pledge.c. There are other exotic setsockopt calls that would
> probably prevent early pledge calls.
>
> Another minor issue is that pidfile(3) installs an atexit(3) handler
> that calls unlink(2). It makes little
.c. There are other exotic setsockopt calls that would
probably prevent early pledge calls.
Another minor issue is that pidfile(3) installs an atexit(3) handler
that calls unlink(2). It makes little sense to have rtadvd slaughtered
when it tries to unlink /var/run/rtadvd.pid, especially as that
On Mon, Jun 07, 2010 at 09:33:34AM +0200, Michael Lechtermann wrote:
> Hi,
>
> >> Well, that makes sense. But what about not showing the arguments
> >> ifstated was started with? Any reason to wipe them? It would really help
> >> to identify the correct process when those are showed.
> >>
> >> Wha
Hi,
>> Well, that makes sense. But what about not showing the arguments
>> ifstated was started with? Any reason to wipe them? It would really help
>> to identify the correct process when those are showed.
>>
>> What I mean is:
>> setproctitle(NULL);
>
> I have asked a two developers why that was
> Am 05.06.2010 18:51, schrieb Theo de Raadt:
> >> since it is possible to supply a config file to ifstated and run it
> >> multiple times with different configs, I thought it nice for it to also
> >> write a pidfile _and_ actually show in ps which arguments it g
Am 05.06.2010 18:51, schrieb Theo de Raadt:
>> since it is possible to supply a config file to ifstated and run it
>> multiple times with different configs, I thought it nice for it to also
>> write a pidfile _and_ actually show in ps which arguments it got.
>
> Whe
> since it is possible to supply a config file to ifstated and run it
> multiple times with different configs, I thought it nice for it to also
> write a pidfile _and_ actually show in ps which arguments it got.
When possible, we don't use pidfiles. You can't do anything with
Hi,
since it is possible to supply a config file to ifstated and run it
multiple times with different configs, I thought it nice for it to also
write a pidfile _and_ actually show in ps which arguments it got.
Below is a diff that does just that. The pidfile part is stolen from
isakmpd
19 matches
Mail list logo
