> No need to mix doubleforking and PID tracking on your
> program. That should be the duty of whatever daemonizes and manages
> your program. You know, like Daemontools or s6.
So there is a very good reason for a deamon to handle its
own backgrounding: The sensible convention is it that it
should
On Sat, 28 Mar 2015, Jude Nelson wrote:
>It's not ready yet--it's not yet ABI-compatible with libudev (but it is
>API-compatible--Kay Sievers' tests pass when recompiled).
ACK
>Some background for the rest of the list.* I've managed to extract
>the required variables, macros, a
Hi!
See this one:
Bug#761658: Please do not default to using Google nameservers
Marco tagged it as "wontfix". Seriously, if I didn´t configure a
nameserver I *mean* it. I don´t want it to just choose a Google nameserver
then, without even telling me.
Ciao,
--
Martin 'Helios' Steigerwald - ht
dear Martin,
On Sun, 29 Mar 2015, Martin Steigerwald wrote:
> Bug#761658: Please do not default to using Google nameservers
tl;dr - isn't there a preseed directive to change the default?!
> Marco tagged it as "wontfix". Seriously, if I didn´t configure a
> nameserver I *mean* it. I don´t want
Am Sonntag, 29. März 2015, 15:26:51 schrieben Sie:
> dear Martin,
Dear Jaromil,
> On Sun, 29 Mar 2015, Martin Steigerwald wrote:
> > Bug#761658: Please do not default to using Google nameservers
>
> tl;dr - isn't there a preseed directive to change the default?!
I have no idea, I think I have r
marc wrote:
> > No need to mix doubleforking and PID tracking on your
> > program. That should be the duty of whatever daemonizes and manages
> > your program. You know, like Daemontools or s6.
>
> So there is a very good reason for a deamon to handle its
> own backgrounding: The sensible conventi
On Sun, 29 Mar 2015 11:15:49 +0200
marc wrote:
> > No need to mix doubleforking and PID tracking on your
> > program. That should be the duty of whatever daemonizes and manages
> > your program. You know, like Daemontools or s6.
>
> So there is a very good reason for a deamon to handle its
> own
On Sun, Mar 29, 2015 at 03:07:43PM +0200, Martin Steigerwald wrote:
> Hi!
>
> See this one:
>
> Bug#761658: Please do not default to using Google nameservers
>
> Marco tagged it as "wontfix". Seriously, if I didn´t configure a
> nameserver I *mean* it. I don´t want it to just choose a Google na
On Sun, Mar 29, 2015 at 11:22:01PM +, KatolaZ wrote:
> On Sun, Mar 29, 2015 at 03:07:43PM +0200, Martin Steigerwald wrote:
> > Hi!
> >
> > See this one:
> >
> > Bug#761658: Please do not default to using Google nameservers
> >
> > Marco tagged it as "wontfix". Seriously, if I didn´t configur
On Sun, Mar 29, 2015 at 08:27:01PM -0400, Hendrik Boom wrote:
> Why I've never understood is why it's not the default for a Debian
> installation to have its own nameserver.
>
> Is there a reason to trust anyone else's nameserver?
Without DNSSEC, it's a fair tradeoff (no caching, but you have on
KatolaZ wrote on 03/29/15 18:22:
> On Sun, Mar 29, 2015 at 03:07:43PM +0200, Martin Steigerwald wrote:
>> Hi!
>>
>> See this one:
>>
>> Bug#761658: Please do not default to using Google nameservers
>>
>> Marco tagged it as "wontfix". Seriously, if I didn´t configure a
>> nameserver I *mean* it. I
11 matches
Mail list logo