On Jan 21, 2014, at 5:32 AM, Carsten Strotmann wrote:
> Hi Chris,
>
> Chris Buxton writes:
>
>> I’d bet that the package from Men & Mice includes this script or an
>> equivalent workaround. When I wrote the original script I wrote about
>> above, I worked at Men & Mice.
>
> Your script or th
On Jan 22, 2014, at 12:27 PM, LuKreme wrote:
>
> Right, but Apple did this by having their compile of bind start listening on
> 127.0.0.1 and then prodding it once the network was up and the IP address was
> available. Since Apple doesn't take this extra step, you'd need to tell
> launchd to
On Jan 21, 2014, at 11:38 PM, LuKreme wrote:
>
> In the launchd plist do you have something like
>
I finally got around to testing both of these.
>
> NetworkState
>
>
>
Had no effect.
> or maybe
>
> inetdCompatibility
>
> Wait
>
>
>
Wouldn’t even start. Repeatedly (about 150
On Wed, 22 Jan 2014, LuKreme wrote:
Right, but Apple did this by having their compile of bind start
listening on 127.0.0.1 and then prodding it once the network was up and
the IP address was available. Since Apple doesn't take this extra step,
you'd need to tell launchd to wait for the Network
On 22 Jan 2014, at 05:37 , Larry Stone wrote:
>
> On Jan 21, 2014, at 11:38 PM, LuKreme wrote:
>
>>
>> On 18 Jan 2014, at 06:52 , Larry Stone wrote:
>>
>>> That is not the problem.
>>
>> In the launchd plist do you have something like
>>
>>
>> NetworkState
>>
>>
>>
>> or maybe
>>
>
On Jan 21, 2014, at 11:38 PM, LuKreme wrote:
>
> On 18 Jan 2014, at 06:52 , Larry Stone wrote:
>
>> That is not the problem.
>
> In the launchd plist do you have something like
>
>
> NetworkState
>
>
>
> or maybe
>
> inetdCompatibility
>
> Wait
>
>
>
> to tell the system not t
On 18 Jan 2014, at 06:52 , Larry Stone wrote:
> That is not the problem.
In the launchd plist do you have something like
NetworkState
or maybe
inetdCompatibility
Wait
to tell the system not to start bind until after the network is up?
--
IT IS NOT YET MIDNIGHT? 'I shouldn'
On Jan 21, 2014, at 5:32 AM, Carsten Strotmann wrote:
> Hi Chris,
>
> Chris Buxton writes:
>
>> I’d bet that the package from Men & Mice includes this script or an
>> equivalent workaround. When I wrote the original script I wrote about
>> above, I worked at Men & Mice.
>
> Your script or th
Hi Chris,
Chris Buxton writes:
> I’d bet that the package from Men & Mice includes this script or an
> equivalent workaround. When I wrote the original script I wrote about
> above, I worked at Men & Mice.
Your script or the sleep timer is not in the package anymore, but maybe
it should be. I d
On Jan 20, 2014, at 1:22 PM, Chris Buxton wrote:
>> Problem: This morning, by happenstance, both were rebooted a few minutes
>> apart and suddenly, nobody could access anything. Finally figured out that
>> named on both was not responding (queries timed out). Killed named (which
>> was immedi
On Jan 17, 2014, at 6:45 PM, Larry Stone wrote:
> Background: I have been using my Macintosh as a server…
[…]
> Problem: This morning, by happenstance, both were rebooted a few minutes
> apart and suddenly, nobody could access anything. Finally figured out that
> named on both was not respond
;bind-users@lists.isc.org"
Sent: Saturday, January 18, 2014 4:15 PM
Subject: Re: Non-responsive name servers when started during boot on OS X
Mavericks 10.9
Eduardo -
You’re not really reading what the problem is. When named is started as part of
system boot, it is running but non-respon
re-start!
>
>
>
>
>
>
> --
> Eduardo Bonsi
> System/Network Admin
> BEARTCOMMUNICATIONS
> beart...@pacbell.net
>
> From: Larry Stone
> To: "bind-users@lists.isc.org"
> Sent: Saturday, January 18, 2014 5:52 AM
> Subject: Re: Non-resp
rvers when started during boot on OS X
Mavericks 10.9
That is not the problem. Named does start at boot but it is non-responsive
(with further thought, perhaps it is for some reason not listening on port 53).
When killed and restarted, it then works fine.
I am not familiar with macshadows.com
That is not the problem. Named does start at boot but it is non-responsive
(with further thought, perhaps it is for some reason not listening on port 53).
When killed and restarted, it then works fine.
I am not familiar with macshadows.com but those directions are incomplete and
and assume the
Hello Larry,
I had the same "head-ache" when I upgraded to 10.9. It seems that instead going
forward we all took a step behind. I guess this type of free stuff does come
with something attached to it. Anyways, when you upgraded to 10.9 the boot
files were wipe clean from the /System/Library/Lau
16 matches
Mail list logo
