On Thu, Jun 13, 2024 at 7:19 AM Michael via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:
> My battery is dead. That don't matter to me because NTP is supposed to set
> the time to the correct time. But it's not. I have to manually go in and
> set the time! Wh
okay. I figured that out create a cron job:
@reboot sudo service ntp stop
@reboot sudo ntpd -gq
@reboot sudo service ntp start
But I can't add my user to sudoers never mind! was putting user in
wrong section! cool.
On Thu, Jun 13, 2024 at 10:18 AM Michael wrote:
> My battery
My battery is dead. That don't matter to me because NTP is supposed to set
the time to the correct time. But it's not. I have to manually go in and
set the time! What's the deal? Is there a way to get NTP to do what it's
suppos
, 07:15 Michael via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:
> oops forgot a step. I had to install ntp which I googled how to do and
> did so successfully.
>
> On Thu, Jan 5, 2023 at 8:31 AM Michael wrote:
>
>> I'm following the directions here
>
oops forgot a step. I had to install ntp which I googled how to do and
did so successfully.
On Thu, Jan 5, 2023 at 8:31 AM Michael wrote:
> I'm following the directions here
> <https://www.how2shout.com/linux/solve-kali-error-inrelease-is-not-valid-yet-invalid-for-another-xh-x
Updates for this
repository will not be applied.
"
So I googled that and learned my clock was off and to restart ntp and
other stuff. I googled how to do that and was directed here
<https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&v
ia PLUG-discuss
<mailto:plug-discuss@lists.phxlinux.org>> wrote:
How does one set it up so that arch doesn't need a cmos battery. Mine
is going belly-up and I don't want to replace it. I was thinking I
shouldn't need to wit
via PLUG-discuss
> wrote:
>
> How does one set it up so that arch doesn't need a cmos battery. Mine is
> going belly-up and I don't want to replace it. I was thinking I shouldn't
> need to with NTP. What
it initially was about NTP. I thought I could reset system time at each
restart. And I believe it is the battery because it often forgets the time.
usually it is only off a couple of hous but a couple of times it has been
off by decades. it has said it was 2031.
On Thu, Dec 23, 2021 at 6:21 PM
aptop. I leave it as an exercise to you how to
find the Youtube video on youtube.com.
There's one other web page you really need to read:
http://www.catb.org/~esr/faqs/smart-questions.html
This was never about NTP, this was about a battery.
Or maybe not, because you never told us wh
ime at boot can cause any number of “wonky” things,
>>> but also opens up some VERY nasty security attacks that revolve around
>>> timing. It is difficult and time consuming to get a system out of time with
>>> NTP running (which it should be by default on most Linux dis
e is correct, you should replace the battery or replace the hardware.
>> An improper time at boot can cause any number of “wonky” things, but also
>> opens up some VERY nasty security attacks that revolve around timing. It is
>> difficult and time consuming to get a system out of
eve is correct, you should replace the battery or replace the hardware.
> An improper time at boot can cause any number of “wonky” things, but also
> opens up some VERY nasty security attacks that revolve around timing. It is
> difficult and time consuming to get a system out of time
Steve is correct, you should replace the battery or replace the hardware. An
improper time at boot can cause any number of “wonky” things, but also opens up
some VERY nasty security attacks that revolve around timing. It is difficult
and time consuming to get a system out of time with NTP
itt via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:
> Michael via PLUG-discuss said on Thu, 23 Dec 2021 12:03:19 -0500
>
> >How does one set it up so that arch doesn't need a cmos battery. Mine
> >is going belly-up and I don't want to replace it. I was think
Michael via PLUG-discuss said on Thu, 23 Dec 2021 12:03:19 -0500
>How does one set it up so that arch doesn't need a cmos battery. Mine
>is going belly-up and I don't want to replace it. I was thinking I
>shouldn't need to with NTP. What do you think?
https://lmgtfy.app/#
How does one set it up so that arch doesn't need a cmos battery. Mine is
going belly-up and I don't want to replace it. I was thinking I shouldn't
need to with NTP. What do you think?
--
:-)~MIKE~(-:
---
PLUG-discuss mailing list
Sorry for my late comment response.
What distribution are you using? The reason I ask is that lets say you
are using CentOS 7, CentOS 7 uses Chrony (http://chrony.tuxfamily.org/)
for its ntp service (installed and running by default) and ntpd will
have all sorts of problems unless you remove
e
> dependencies or something? Here's the first bit of the init.d again:
> ### BEGIN INIT INFO
> # Provides:ntp
> # Required-Start: $network $remote_fs $syslog
> # Required-Stop: $network $remote_fs $syslog
> # Default-Start: 2 3 4 5
> # Default-Stop:
> # Sh
BEGIN INIT INFO
# Provides: ntp
# Required-Start: $network $remote_fs $syslog
# Required-Stop: $network $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop:
# Short-Description: Start NTP daemon
### END INIT INFO
On Tue, Sep 8, 2015 at 7:23 PM, Tejeev Patel wrote:
> Hi all,
Hi all,
Thanks for your replies James and Hans. I've included some responses in
the bellow email:
> moin moin TJ,
>
> what James said in regards to debugging ntp :).
>
Ill check on these step tickers, but my understanding was that the -g
option should take care of that. Can I
wätzte Tejeev Patel so:
>
> moin moin TJ,
>
> what James said in regards to debugging ntp :).
>
> Here are some other things to check.
>
> Is there some ntp process already running?
>
> ps auxw | grep ntp
>
> Is there a config file in /etc/default/ that has an entry
Am 04. Sep, 2015 schwätzte Tejeev Patel so:
moin moin TJ,
what James said in regards to debugging ntp :).
Here are some other things to check.
Is there some ntp process already running?
ps auxw | grep ntp
Is there a config file in /etc/default/ that has an entry to not start
ntp?
Is
ntp is suppose to do a step initially to force time before it turns on.
it's possible you're so far out of sync it just forgets itself.
another possibility is that you're not able to contact the ntp servers in
question.
ntpq -c opeers to see what it thinks is going on while runni
I've got all of my servers running ntp to sync time, and though most are
running fine without a hitch, I seem to have an issue where for some reason
the service just doesn't start on some of them. Same install procedure on
all servers. No errors in syslog or ntp for days, even when
25 matches
Mail list logo
