I wasn't talking about (or even really looking at, at the time) the
output of rndc -help. I was originally discussing the description in
the Administrators Reference Manual for Bind 9.4.
-rich
On Jan 23, 2009, at 1:45 AM, Doug Barton wrote:
Niall O'Reilly wrote:
On Wed, 2009-01-21 at 1
Niall O'Reilly wrote:
> On Wed, 2009-01-21 at 19:14 -0600, Jeremy C. Reed wrote:
>> Maybe we should just remove the "immediately" part.
>>
>> Any suggestions would be appreciated.
>
> If you're going to make a change, adding a little more
> information wouldn't hurt, would it?
The ou
On Wed, 2009-01-21 at 19:14 -0600, Jeremy C. Reed wrote:
> Maybe we should just remove the "immediately" part.
>
> Any suggestions would be appreciated.
If you're going to make a change, adding a little more
information wouldn't hurt, would it? Perhaps:
s/immediately/cle
Jeremy C. Reed wrote:
> On Wed, 21 Jan 2009, Rich Goodson wrote:
>
>> And I'm expected to know this, how?
Rich, you read into the text what you wanted it to say (as you
indicated in another message) but failed to try to understand what was
actually there. The behavior you're saying you thought th
I think that the word "immediately" needs to stay, as that's what
differentiates "halt" from "stop".
The documentation in its current form seems to imply that named
returns a signal to rndc as it's exiting.
Perhaps even a simple change such as:
"If -p is specified named’s process id is ret
In article ,
"Jeremy C. Reed" wrote:
> On Wed, 21 Jan 2009, Rich Goodson wrote:
>
> > And I'm expected to know this, how? (incidentally, I added a 'wait'
> > statement to my script after I discovered this behavior). This behavior
> > does not appear to be what the documentation describes, i
On Wed, 21 Jan 2009, Rich Goodson wrote:
> And I'm expected to know this, how? (incidentally, I added a 'wait'
> statement to my script after I discovered this behavior). This behavior
> does not appear to be what the documentation describes, is all I'm
> trying to say.
Just to clarify the d
In message <1a345677-0c03-45a7-a1e1-af364fe87...@gronkulator.com>, Rich Goodson
writes:
> Basically, I'm trying to use a shell script to replace the missing
> 'restart' argument to rndc, so I was looking for some sort of return
> value that tells me, "hey, your old named process is now gone
And I'm expected to know this, how? (incidentally, I added a 'wait'
statement to my script after I discovered this behavior). This
behavior does not appear to be what the documentation describes, is
all I'm trying to say.
And with that, I'm going to drop it before I start acting like a
Rich Goodson wrote:
>> If -p is specified named's process id is returned. This allows an
>> external process to determine when named had completed halting.
>
> Whether named is still answering queries or just cleaning up its
> allocated memory, the PID is returned BEFORE named is gone, as named i
Basically, I'm trying to use a shell script to replace the missing
'restart' argument to rndc, so I was looking for some sort of return
value that tells me, "hey, your old named process is now gone, feel
free to start a new one".
What doesn't seem to jibe to me with the behavior I see is
In message <2971f259-4897-48f8-b418-2f7599075...@gronkulator.com>, Rich Goodson
writes:
> The behavior of 'rndc halt -p' appears to be different from the =20
> documentation.
>
> According to the BIND 9.4 ARM rndc section:
> halt [-p] Stop the server immediately. Recent changes made through =20
The behavior of 'rndc halt -p' appears to be different from the
documentation.
According to the BIND 9.4 ARM rndc section:
halt [-p] Stop the server immediately. Recent changes made through
dynamic update or IXFR
are not saved to the master files, but will be rolled forward from the
journal
13 matches
Mail list logo
