* Stroller (strol...@stellar.eclipse.co.uk) [16.02.09 02:10]:
>
> On 15 Feb 2009, at 21:51, Sebastian Günther wrote:
>> * Stroller (strol...@stellar.eclipse.co.uk) [14.02.09 08:29]:
>>>
>>> On 4 Feb 2009, at 13:40, Justin wrote:
>>>
>>> Except that here, ntp-client seems to start *before* the netwo
On 15 Feb 2009, at 21:51, Sebastian Günther wrote:
* Stroller (strol...@stellar.eclipse.co.uk) [14.02.09 08:29]:
On 4 Feb 2009, at 13:40, Justin wrote:
Except that here, ntp-client seems to start *before* the network,
so fails
to find the ntp-server.
I'll investigate this more later.
If
* Stroller (strol...@stellar.eclipse.co.uk) [14.02.09 08:29]:
>
> On 4 Feb 2009, at 13:40, Justin wrote:
>
> Except that here, ntp-client seems to start *before* the network, so fails
> to find the ntp-server.
>
> I'll investigate this more later.
>
> Stroller.
>
>
>
If you have baselayout2 and op
On 4 Feb 2009, at 13:40, Justin wrote:
pkg_postinst() {
ewarn "You can find an example /etc/ntp.conf in /usr/share/ntp/"
ewarn "Review /etc/ntp.conf to setup server info."
ewarn "Review /etc/conf.d/ntpd to setup init.d info."
echo
elog "The way ntp sets a
On Wed, Feb 04, 2009 at 06:20:50PM +, Stroller wrote:
>
> On 4 Feb 2009, at 14:11, Neil Bothwick wrote:
>> On Wed, 4 Feb 2009 13:38:11 +, Stroller wrote:
>>
>>> So when I found the clock to be a week out of date I checked that ntpd
>>> appeared to be running (it was) and restarted it. The d
On Thu, 2009-02-05 at 13:04 +, Stroller wrote:
> On 4 Feb 2009, at 21:29, Drew Tomlinson wrote:
> > ...
> > To avoid running ntp-client and ntpd, look at the -g switch for ntpd.
> > It will make the big jump once and then keep the clock in sync.
>
>
> So NTPD_OPTS="-g" in /etc/conf.d/ntpd ?
>
On 4 Feb 2009, at 21:29, Drew Tomlinson wrote:
...
To avoid running ntp-client and ntpd, look at the -g switch for ntpd.
It will make the big jump once and then keep the clock in sync.
So NTPD_OPTS="-g" in /etc/conf.d/ntpd ?
Stroller.
Neil Bothwick wrote:
> On Wed, 4 Feb 2009 13:38:11 +, Stroller wrote:
>
>
>> So when I found the clock to be a week out of date I checked that ntpd
>> appeared to be running (it was) and restarted it. The date remained
>> the same. Stopping ntpd & starting ntp-client corrected the date
On 4 Feb 2009, at 18:23, Justin wrote:
Stroller wrote:
On 4 Feb 2009, at 13:40, Justin wrote:
Stroller schrieb:
...
I understood that ntpd was not only a server for my LAN (a
facility I
don't use) but that it would also periodically check the time with
upstream servers & keep the machine'
Stroller wrote:
>
> On 4 Feb 2009, at 13:40, Justin wrote:
>> Stroller schrieb:
>>> ...
>>> I understood that ntpd was not only a server for my LAN (a facility I
>>> don't use) but that it would also periodically check the time with
>>> upstream servers & keep the machine's clock in constant sync.
On 4 Feb 2009, at 14:11, Neil Bothwick wrote:
On Wed, 4 Feb 2009 13:38:11 +, Stroller wrote:
So when I found the clock to be a week out of date I checked that
ntpd
appeared to be running (it was) and restarted it. The date remained
the same. Stopping ntpd & starting ntp-client corrected
On 4 Feb 2009, at 13:40, Justin wrote:
Stroller schrieb:
...
I understood that ntpd was not only a server for my LAN (a facility I
don't use) but that it would also periodically check the time with
upstream servers & keep the machine's clock in constant sync.
...
pkg_postinst() {
ewarn
Am Mittwoch, 4. Februar 2009 14:57:28 schrieb Alan McKinnon:
> ntpd is really designed for Unix servers with 3 digit uptimes and clocks
> not assembled by Mickey Mouse's younger brother (which seems to include all
> pcs ever made.)
Errh, no. It is designed for exactly those machines, so that
Stroller wrote:
> Hi there,
>
> I just logged into one of my machines that has recently been powered
> down for a few days - not a terribly common occurrence with my servers
> - to find a date of January 30th showing.
>
> I used to run ntp-client, but AIUI adding this to the default runlevel
> only
On Wed, 4 Feb 2009 13:38:11 +, Stroller wrote:
> So when I found the clock to be a week out of date I checked that ntpd
> appeared to be running (it was) and restarted it. The date remained
> the same. Stopping ntpd & starting ntp-client corrected the date
> immediately.
ntpd will not c
On Wednesday 04 February 2009 15:38:11 Stroller wrote:
> Before I do any investigation, can someone tell me if my understanding
> so far is correct? Is ntpd supposed to keep the machine's clock in
> constant sync, or is it only (say) a server to offer the date to
> clients? (depending upon th
Stroller schrieb:
> Hi there,
>
> I just logged into one of my machines that has recently been powered
> down for a few days - not a terribly common occurrence with my servers -
> to find a date of January 30th showing.
>
> I used to run ntp-client, but AIUI adding this to the default runlevel
>
Hi there,
I just logged into one of my machines that has recently been powered
down for a few days - not a terribly common occurrence with my servers
- to find a date of January 30th showing.
I used to run ntp-client, but AIUI adding this to the default runlevel
only sets the clock once a
18 matches
Mail list logo
