On 01/09/2016 21:12, Daniel Kahn Gillmor wrote:
I think we might be approaching diminishing returns on this thread, so
please don't take offense if i don't reply too much beyond this.
Are you kidding? We're just getting started. I haven't had a good
design discussion for ages! :D
This doesn
On Sun 2016-09-04 09:36:38 -0400, Laurent Bercot wrote:
> No, because the daemon doesn't care about the numbers, it cares about
> the use case. The daemon doesn't want to know what fd 3 is about, it wants
> to know what fd it should perform UDP socket operations on.
> If you want to provide sev
Simon McVittie:
This can already work. If you put XDG_RUNTIME_DIR in user programs'
environment, and arrange for your favourite service manager to make a
dbus-daemon (or something else that speaks the same protocol) listen
on $XDG_RUNTIME_DIR/bus before any user process would try to connect
t
Just so everyone knows. This didn't get ignored. Guillermo has been
quietly playing with 1.29 behind the scenes.
This was a mixture of things. 1.29 will have (already has) some fixes
for the genuine bugs and for some of the things which are the subject of
much debate. (-:
The fprintf()s
Daniel Kahn Gillmor wrote:
So i'm hoping that it'll find a taker in one of these more
toolkit-style supervisor suites.
http://jdebp.eu./Softwares/nosh/#Features
socket services section
Daniel Kahn Gillmor:
#!/bin/sh
mkdir -p /run/kresd/workdir && \
setfacl -m u:kresd:rwx /run/kresd/workdir && \
cd /run/kresd/workdir && \
exec listen -udp::53 \
-tcp::53 \
-tcp:label=tls:853 \
-unix:label=control,mode=06
