- ntp errors ---
A
href=http://www.listbox.com/member/archive/184463/2014/06/search/bnRw/sort/time_rev/page/1/entry/9:10/;Post
on smartos-discuss/A
I am currently running 20140501T2256422 on a Dell Precision T3500
I know this thread was posted with 2014-06-26 version of
On 11 July 2014 00:02, JJ Stiff via smartos-discuss
smartos-discuss@lists.smartos.org wrote:
Error: Servers/peers specified but none is reachable.
This behaviour has been remedied with an upgrade of the NTP software
we ship, and a retooling of the way we generate ntp.conf. I have put
back the
I've had issues from time caused by the fact that /bin/sh is a symlink
to ksh93 and not bash.
There's sadly a large amount of code out there that puts #!/bin/sh at
the top but actually uses bash-isms...
-Nahum
On 07/10/2014 09:16 PM, Alain O'Dea via smartos-discuss wrote:
-BEGIN PGP
* On 2014-07-11 at 13:28 BST, Nahum Shalman via smartos-discuss wrote:
I've had issues from time caused by the fact that /bin/sh is a
symlink to ksh93 and not bash.
There are also a number of bugs in the ksh93 currently available in
illumos. They are fixed in newer releases, but I don't think
Thanks for helping us solve this issue.
In our use case, we need the NULL_RPC timeout to be at least lower than the
client LOCK request timeout…otherwise our client Mac processes stall/fail
–that’s the real pain point we need to solve.
We don’t see any use that in which the illumos server
I’ve been fighting with this for a while, too. Even with all these changes in
place, I can’t seem to confirm that ntpd is working properly. Should ‘ntpq -p’
report a list of connected peers with the default config? Every time I try the
request times out.
—jason
On Friday, July 11, 2014 at
