diff options
author | 2021-03-16 09:00:43 +0000 | |
---|---|---|
committer | 2021-03-16 09:00:43 +0000 | |
commit | 1ff4cf56fdff3473d72fc4b29d69428c688d47c6 (patch) | |
tree | d6185ab1c66554741635782727a7ca20d4409ebd /usr.bin/tmux/control-notify.c | |
parent | A socket buffer is not the best size to read from a disk. (diff) | |
download | wireguard-openbsd-1ff4cf56fdff3473d72fc4b29d69428c688d47c6.tar.xz wireguard-openbsd-1ff4cf56fdff3473d72fc4b29d69428c688d47c6.zip |
Do not delete control socket upon exit
The control socket is not unveiled, therefore accounting would report
unveil violations whenever apmd(8) stopped (normally).
As discussed and done with other daemons such as relayd which also employ
no pledge (due to inherent limitations) but unveil effecting all of /,
simply stop removing the socket upon exit and leave it to the next apmd
which completely sets up its control socket anew at startup.
Violations reported by anton
Feedback OK semarie mestre
Diffstat (limited to 'usr.bin/tmux/control-notify.c')
0 files changed, 0 insertions, 0 deletions