On Wed, 17 Nov 2010 00:20:01 +0100, Stefan G. Weichinger wrote about
Re: [gentoo-user] bind-9.7.1_p2 does not want to stop...:
>Am 2010-11-16 21:55, schrieb Alan McKinnon:
>
>> I've seen the weirdest inexplicable things from bind (and vixie-cron
>> too, now that I think
Apparently, though unproven, at 01:12 on Wednesday 17 November 2010, Stefan G.
Weichinger did opine thusly:
> Am 2010-11-16 21:55, schrieb Alan McKinnon:
> > I've seen the weirdest inexplicable things from bind (and vixie-cron too,
> > now that I think of it).
>
> OT: what is your recommended al
>
> The problem is, it runs forever, and does not want to stop:
>
Standard practice for any daemon that doesnt want to stop via the init
script, most graceful to most forceful;
1. Try the daemons native shutdown command (some have an option to shutdown
only after any connected clients are serviced
Am 2010-11-16 21:55, schrieb Alan McKinnon:
> I've seen the weirdest inexplicable things from bind (and vixie-cron too, now
> that I think of it).
OT: what is your recommended alternative to vixie-cron then?
thx, S
Apparently, though unproven, at 22:37 on Tuesday 16 November 2010, Jarry did
opine thusly:
> > Failing that, there's "kill -9", this won't break anything but might
> > disconnect a client.
>
> Well, I could kill the process while working in terminal. But when
> I forget to do it and try to shutd
On 16. 11. 2010 20:47, Alan McKinnon wrote:
Do you absolutely *have* to run bind? Aside from it being a 100% RFC-compliant
reference server, it's a pig to run in real life. For an auth server, powerdns
is very good. For a cache, unbound.
Well, not *absolutely*, but I'm an old dog used to work
Apparently, though unproven, at 21:17 on Tuesday 16 November 2010, Jarry did
opine thusly:
> Hi,
> today I updated my bind from 9.4.3_p5 to 9.7.1_p2. I noticed
> a few changes in configuration so first I did full backup, then
> uninstalled 9.4.3_p5 first, removed all configuration files,
> then e
Hi,
today I updated my bind from 9.4.3_p5 to 9.7.1_p2. I noticed
a few changes in configuration so first I did full backup, then
uninstalled 9.4.3_p5 first, removed all configuration files,
then emerged 9.7.1_p2, and configured it to run from chroot.
named seems to start normally:
# /etc/init.d
8 matches
Mail list logo
