You're welcome!
On Fri, 13 Jun 2003 12:08:10 + (UTC)
Juri Haberland <[EMAIL PROTECTED]>
wrote:
"brett holcomb" <[EMAIL PROTECTED]> wrote:
No, the network is running before local.start is
executed.
Local is last to start up and first to go down.
Ok, I stand corrected ;)
Cheers,
Juri
--
J
"brett holcomb" <[EMAIL PROTECTED]> wrote:
> No, the network is running before local.start is executed.
> Local is last to start up and first to go down.
Ok, I stand corrected ;)
Cheers,
Juri
--
Juri Haberland <[EMAIL PROTECTED]>
--
[EMAIL PROTECTED] mailing list
On Thursday 12 June 2003 11:26 am, David wrote:
> That is that way I understood it. I never did try try ntpd and with ntpdate
> in my local.start. That probably would have corrected my problems, but
> ntpdate seems to be working fine by itself right now. Interesting
> conversation on the subject
On Thursday 12 June 2003 10:29 am, Paul de Vrieze wrote:
> On Thursday 12 June 2003 16:04, [EMAIL PROTECTED] wrote:
> > On Thu, Jun 12, 2003 at 03:54:40PM +0200, Paul de Vrieze wrote:
> > Content-Description: signed data
> >
> >
> > My understanding is that a combination of the two works well - and
No, the network is running before local.start is executed.
Local is last to start up and first to go down.
On Thu, 12 Jun 2003 15:43:00 + (UTC)
Juri Haberland <[EMAIL PROTECTED]>
wrote:
David <[EMAIL PROTECTED]> wrote:
Correct. Never said it did. It is in the local.start and
only runs at
[EMAIL PROTECTED] ~ $ date ; echo ${Juri Haberland}
Thursday 12 June 2003 12:43 pm
> I might be wrong, but I think local.start is executed *before* the
> network has started, so ntpdate can't connect to any server.
AFTER. It's the last script to be run on boot up.
Regards,
Norberto
pgp0.pg
David <[EMAIL PROTECTED]> wrote:
>>ntpdate should only be run on system boot
>>time to initially set the correct time. It was never meant to keep the
>>time continously up-to-date.
>
> Correct. Never said it did. It is in the local.start and only runs at startup.
I might be wrong, but I think loc
>ntpdate should only be run on system boot
>time to initially set the correct time. It was never meant to keep the
>time continously up-to-date.
Correct. Never said it did. It is in the local.start and only runs at startup.
--
[EMAIL PROTECTED] mailing list
Yes, I would agree on that. I don't think it contradicts any of my previous
statements or ideas either.
>
> That is correct. At bootup time no applications are running that would
> suffer from a time lapse, so then ntpdate is safe. Running ntpdate from a
> cronjob though, is not.
>
> Paul
--
[EM
That is that way I understood it. I never did try try ntpd and with ntpdate in
my local.start. That probably would have corrected my problems, but ntpdate
seems to be working fine by itself right now. Interesting conversation on the
subject though.
Dave
> >
> > I don't know but the use of ntpd is
David <[EMAIL PROTECTED]> wrote:
> I had 3 servers and when looking in the logs, saw a lot of
> connection problems. Also, system was showing problem stopping
> the ntpd when shutting down or rebooting.
Then either the servers you choose didn't allow you to get the time or
you configured ntpd wron
On Thursday 12 June 2003 16:04, [EMAIL PROTECTED] wrote:
> On Thu, Jun 12, 2003 at 03:54:40PM +0200, Paul de Vrieze wrote:
> Content-Description: signed data
>
>
> My understanding is that a combination of the two works well - and
> that's reflected in the gentoo (and other distros) ntpd startup sc
On Thu, Jun 12, 2003 at 03:54:40PM +0200, Paul de Vrieze wrote:
Content-Description: signed data
> On Thursday 12 June 2003 15:33, David wrote:
> > I had 3 servers and when looking in the logs, saw a lot of
> > connection problems. Also, system was showing problem stopping
> > the ntpd when shuttin
On Thursday 12 June 2003 15:33, David wrote:
> I had 3 servers and when looking in the logs, saw a lot of
> connection problems. Also, system was showing problem stopping
> the ntpd when shutting down or rebooting.
> If I would check the server it was usually fine from my memory.
> Also, I think it
I had 3 servers and when looking in the logs, saw a lot of
connection problems. Also, system was showing problem stopping
the ntpd when shutting down or rebooting.
If I would check the server it was usually fine from my memory.
Also, I think it would depend on if your system keeps time well or not.
On Wednesday 11 of June 2003 18:09, David wrote:
> You can remove it from boot with:
> rc-update del ntpd default
>
> I stopped using ntpd and just put ntpdate in my /etc/conf.d/local.start
> file.
>
> # ntpd doesn't work to well so use this for clock setting
> ntpdate ntp0.mcs.anl.gov
>
> not sure
David <[EMAIL PROTECTED]> wrote:
> You can remove it from boot with:
> rc-update del ntpd default
>
> I stopped using ntpd and just put ntpdate in my /etc/conf.d/local.start file.
>
> # ntpd doesn't work to well so use this for clock setting
> ntpdate ntp0.mcs.anl.gov
>
> not sure if this would
Finally figured it out. I was stuck at the boot, but found out how to
boot single user mode via grub and then removed it alla rc-update. All
is good now
I will take your advice about adding ntpdate to my local.start.
Although I think adding to Cron would be better. I'll try both.:)
Thanks fo
You can remove it from boot with:
rc-update del ntpd default
I stopped using ntpd and just put ntpdate in my /etc/conf.d/local.start file.
# ntpd doesn't work to well so use this for clock setting
ntpdate ntp0.mcs.anl.gov
not sure if this would stop the problem if it cannot connect to the server
Silly situation, but I just set up ntpd
at work, and now I am off site trying to serial connect into a Nortel
Switch. Thing is Gentoo hangs at boot
trying to sync ntpd.
Is there any possible way to get past this at boot time, or
disable it during the boot.
Any advice is appreci
20 matches
Mail list logo
