On 3/27/22, Greg Wooledge wrote:
> Well, you are. Just not in the normal way.
On 3/27/22, to...@tuxteam.de wrote:
> Debian Live /is/ a dual boot -- unless the computer in question
> has no operating system to begin with :-)
>
> I think there is some misunderstanding on how songbird and you
> th
On Sun 27 Mar 2022 at 18:29:35 (+), Albretch Mueller wrote:
> On 3/27/22, songbird wrote:
> > set the bios time to be universal and then set up windows
> > to use universal time.
>
> again, assumptions ...
>
> On 3/27/22, David Wright wrote:
> > It looks as if you're dual-booting.
>
>
On Sun, Mar 27, 2022 at 06:29:35PM +, Albretch Mueller wrote:
> On 3/27/22, David Wright wrote:
> > It looks as if you're dual-booting.
>
> No, I am not.
Well, you are. Just not in the normal way.
You've got one OS permanently installed on the disk, and one on a
removable device. That's
On Sun, Mar 27, 2022 at 06:29:35PM +, Albretch Mueller wrote:
> On 3/27/22, songbird wrote:
> > set the bios time to be universal and then set up windows
> > to use universal time.
>
> again, assumptions ...
>
> On 3/27/22, David Wright wrote:
> > It looks as if you're dual-booting.
>
>
On 3/27/22, songbird wrote:
> set the bios time to be universal and then set up windows
> to use universal time.
again, assumptions ...
On 3/27/22, David Wright wrote:
> It looks as if you're dual-booting.
No, I am not.
Use case: I keep a DL DVD with me as some sort of cross between
defe
On Sun 27 Mar 2022 at 06:31:16 (+), Albretch Mueller wrote:
> $ uname -a
> Linux debian 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08)
> x86_64 GNU/Linux
> $
> and how can I avoid that from happening?
It looks as if you're dual-booting. Whenever I've had
a period of doing that, I start
Albretch Mueller wrote:
> $ uname -a
> Linux debian 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08)
> x86_64 GNU/Linux
> $
> and how can I avoid that from happening?
> lbrtchx
set the bios time to be universal and then set up windows
to use universal time.
and no, i don't know how to s
ase for many DL users on a
Windows install base.
Another way to find a solution around such "political" decisions
would be to include an utility on DL to reset the time based on NTP
(and/or the location of the user ...).
lbrtchx
On Sun, Mar 27, 2022 at 12:08:38PM +, Albretch Mueller wrote:
> On 3/27/22, to...@tuxteam.de wrote:
> > (3) Hardware clock gets adjusted accordingly.
> > [which] would be
> > wrong for a live distro: don't touch persistent state!
>
> exactly! will this set up "logic" be fixed for the next li
On 3/27/22, to...@tuxteam.de wrote:
> (3) Hardware clock gets adjusted accordingly.
> [which] would be
> wrong for a live distro: don't touch persistent state!
exactly! will this set up "logic" be fixed for the next live systems?
lbrtchx
al-rtc 1 and offers no
ways to prevent what is described in
https://www.kernel.org/doc/html/latest/admin-guide/rtc.html
"if the kernel time is synchronized with an external source,
the kernel will write the time back to the CMOS clock every
11 minutes."
man 4 rtc does not of
em arises that it must know whether
> the hardware clock is meant to be set to UTC or to local time.
Perhaps, but perhaps it shouldn't /set/ the hardware clock. What seems
to be happening is:
(0) hardware clock is set to local time (bad habits [1] die hard)
(1) Debian Live boots, picks up
Hi,
Albretch Mueller wrote:
> The use of a live DVD at times is
> necessary, but part of very idea of going live is not altering, having
> to alter the hard- or firmware, right?
That's a valid point. It should be discussed on debian-live, i guess.
Google shows me that the problem can be avoided
On 3/27/22, David Christensen wrote:
> I have a desktop machine (Intel DQ67SW motherboard) with a 2.5" SATA
> trayless drive rack that I boot with various OS's on 2.5" SATA SSD's. I
> have to remember to enter Setup and adjust the CMOS clock every time I
> switch between a FOSS OS and Windows.
On 3/26/22 23:31, Albretch Mueller wrote:
$ uname -a
Linux debian 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08)
x86_64 GNU/Linux
$
and how can I avoid that from happening?
lbrtchx
I have a desktop machine (Intel DQ67SW motherboard) with a 2.5" SATA
trayless drive rack that I boot w
$ uname -a
Linux debian 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08)
x86_64 GNU/Linux
$
and how can I avoid that from happening?
lbrtchx
> That makes sense.These WD drives I got to sleep automatically after 10m are
> 2013 Blue desktop drives.
There's a chance that you just got lucky and the time that the drive
decides to use is similar to the time you set. In any case this
behavior was not really documented anywhere
h some
> > respond better than others. I've been able to set the sleep time in WD
> > drives but not Seagate, but both go to sleep when instructed.
>
> FWIW, the `hdparm -S` doesn't really work for WD drives last I checked.
> More specifically, IIUC WD drives will mostly di
ast I checked.
More specifically, IIUC WD drives will mostly disregard the "time to spin
down" you specify and instead they'll use their own idea of what the
time to spin down should be based on the power-management level
you specified.
Stefan
Hi,
another option is hd-idle package available via backports for stable and
oldstable.
On 11/12/20 1:18 PM, Thomas Anderson wrote:
Hello List,
I have two drives (setup in a RAID 1 array).
The drives are mostly for archive purposes, and accessible via SMB on my
local network.
They are not
Sorry it's 'hdparm -S' to set sleep time, not small s!
--
James B
portoteache...@fastmail.com
Em Qui, 12 Nov ʼ20, às 12:25, James B escreveu:
> You can set the sleep time in the firmware of most drives, although
> some respond better than others. I've been able to set the sleep time
> in
You can set the sleep time in the firmware of most drives, although some
respond better than others. I've been able to set the sleep time in WD drives
but not Seagate, but both go to sleep when instructed. I have an old Iomega
ix2-200 running Arch ARM.I use 'hdparm' to instruct the drives to sle
Hello List,
I have two drives (setup in a RAID 1 array).
The drives are mostly for archive purposes, and accessible via SMB on my
local network.
They are not constantly accessed, and performance/speed is irrelevant.
I would rather they idle/sleep when not being directly accessed. I know
they ar
On Mon, Jul 10, 2017, at 09:19 AM, Fungi4All wrote:
>
>> From: mattcr...@mattcrews.com
>> To: Fungi4All
>> debian-user@lists.debian.org
>>
>> Back up your ~/.mozilla folder, delete it and reopen Firefox. This will
>> create a fresh Firefox profile. Make sure that Firefox's built in pop up
>> b
> From: mattcr...@mattcrews.com
> To: Fungi4All
> debian-user@lists.debian.org
>
> Back up your ~/.mozilla folder, delete it and reopen Firefox. This will
> create a fresh Firefox profile. Make sure that Firefox's built in pop up
> blocker is enabled. Then navigate to websites that are generatin
" wrote:
UTC Time: July 10, 2017 12:27 PM
From: anilduggir...@fastmail.fm
To: debian-user@lists.debian.org
On Mon, Jul 10, 2017, at 02:43 AM, Dejan Jocic wrote:
> On 09-07-17, Anil Duggirala wrote:
> > hello,
> > Ever since I moved to Stretch I have had pop-up windows popping
On 7/10/17, Anil Duggirala wrote:
> On Mon, Jul 10, 2017, at 02:43 AM, Dejan Jocic wrote:
>> On 09-07-17, Anil Duggirala wrote:
>> > hello,
>> > Ever since I moved to Stretch I have had pop-up windows popping up all
>> > the time (clicking on various it
> UTC Time: July 10, 2017 12:27 PM
> From: anilduggir...@fastmail.fm
> To: debian-user@lists.debian.org
> On Mon, Jul 10, 2017, at 02:43 AM, Dejan Jocic wrote:
>> On 09-07-17, Anil Duggirala wrote:
>> > hello,
>> > Ever since I moved to Stretch I have had po
On Mon, Jul 10, 2017, at 02:43 AM, Dejan Jocic wrote:
> On 09-07-17, Anil Duggirala wrote:
> > hello,
> > Ever since I moved to Stretch I have had pop-up windows popping up all
> > the time (clicking on various items on various types of pages). I am
> > posting here, s
On 09-07-17, Anil Duggirala wrote:
> hello,
> Ever since I moved to Stretch I have had pop-up windows popping up all
> the time (clicking on various items on various types of pages). I am
> posting here, since this is only happening in my Debian installation.
> Was anything changed
hello,
Ever since I moved to Stretch I have had pop-up windows popping up all
the time (clicking on various items on various types of pages). I am
posting here, since this is only happening in my Debian installation.
Was anything changed in the default configuration of Firefox. It feels
like
On Wed, Jan 18, 2017 at 11:06:06AM -0500, Felix Miata wrote:
> Date: Wed, 18 Jan 2017 11:06:06 -0500
> From: Felix Miata
> To: debian-user@lists.debian.org
> Subject: Re: Stretch changes the time of my laptop
> Gerard ROBIN composed on 2017-01-18 14:33 (UTC+0100):
>
> >
Lisi Reisz wrote:
> On Wednesday 18 January 2017 13:33:38 Gerard ROBIN wrote:
>> Hello,
>> I installed stretch on a external usb hard drive and when I boot on the
>> had drive and I shut down, then I boot again, but on the internal hard
>> drive, with jessie, the
Gerard ROBIN composed on 2017-01-18 14:33 (UTC+0100):
I installed stretch on a external usb hard drive and when I boot on the
had drive and I shut down, then I boot again, but on the internal hard
drive, with jessie, the time is delayed by one hour.
I would like to know if this is normal
On Wednesday 18 January 2017 13:33:38 Gerard ROBIN wrote:
> Hello,
> I installed stretch on a external usb hard drive and when I boot on the
> had drive and I shut down, then I boot again, but on the internal hard
> drive, with jessie, the time is delayed by one hour.
>
> I wou
Hello,
I installed stretch on a external usb hard drive and when I boot on the
had drive and I shut down, then I boot again, but on the internal hard
drive, with jessie, the time is delayed by one hour.
I would like to know if this is normal, and if not what can I do to fix
the problem
Dennis Wicks writes:
> Mart van de Wege wrote on 07/27/2015 12:49 AM:
>> Gary Dale writes:
>>
>>> On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale writes:
>>> Upgrading to sid is asking for trouble. Sid isn't called unstable for
>>> nothing.
>>
>> I know. I really do. I only ha
Mart van de Wege wrote on 07/27/2015 12:49 AM:
Gary Dale writes:
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale writes:
Upgrading to sid is asking for trouble. Sid isn't called unstable for
nothing.
I know. I really do. I only have been running Debian since potato. On
the other
Renaud (Ron) OLGIATI wrote on 07/26/2015 03:40 PM:
On Sun, 26 Jul 2015 15:27:50 -0500
John Hasler wrote:
I want to be able to set the time if for some reason the clock is
completely incorrect (this occurred from time to time in the past).
Use your wristwatch.
Or better, your cellphone or
Gary Dale writes:
> On 26/07/15 02:44 PM, Mart van de Wege wrote:
>> Gary Dale writes:
>>
> Upgrading to sid is asking for trouble. Sid isn't called unstable for
> nothing.
I know. I really do. I only have been running Debian since potato. On
the other hand, someone's gotta run Sid, or it'll ne
On 26/07/15 02:44 PM, Mart van de Wege wrote:
Gary Dale writes:
I haven't had any significant problems with systemd but then I waited
several months before upgrading my servers to jessie and before
upgrading my workstation to stretch. Maybe it's because of MS-DO but
I've learned to wait for th
On Sun, Jul 26, 2015 at 09:34:46PM -0400, The Wanderer wrote:
> On 07/26/2015 at 08:51 PM, Chris Bannister wrote:
>
> > On Sun, Jul 26, 2015 at 12:02:07PM -0400, Gary Dale wrote:
>
> >> Much of this discussion reminds me of an old Monty Python skit
> >> ending with the line "Lucky we didn't say a
On 07/26/2015 at 08:51 PM, Chris Bannister wrote:
> On Sun, Jul 26, 2015 at 12:02:07PM -0400, Gary Dale wrote:
>> Much of this discussion reminds me of an old Monty Python skit
>> ending with the line "Lucky we didn't say anything about the dirty
>> knife". :)
>
> IIRC, it was a dirty fork.
N
On Sun, Jul 26, 2015 at 12:02:07PM -0400, Gary Dale wrote:
> On 26/07/15 10:45 AM, John Hasler wrote:
> >>It may have been an X-Y question, but the answer to the question
> >>actually asked, was "ntp".
> >That is *an* answer. The full answer is that the Chrony and Ntp
> >packages provide time daem
On Sun, 26 Jul 2015, Gary Dale wrote:
Much of this discussion reminds me of an old Monty
Python skit ending with the line "Lucky we didn't
say anything about the dirty knife". :)
I don't recall that bit, but then NO ONE EXPECTS THE
SPANISH INQUISITION!
Recently I checked out the price of
On Sun, 26 Jul 2015, John Hasler wrote:
Systemd-timesyncd is not a replacement for Ntpd or
Chrony. It is just an SNTP client similar to that
used by Microsoft. It queries a single server and
does no error checking or authentication.
Basically, it replaces a cron job running Ntpdate.
A ver
On Sun, 26 Jul 2015, Lisi Reisz wrote:
The question was:
"What package contains the time daemon?"
It may have been an X-Y question, but the answer to
the question actually asked, was "ntp".
You are (again) stunningly correct Lisi. I don't seem
to have been able
John Hasler wrote:
The Wanderer writes:
The original question was "What package contains the daemon that
updates the time from a central site?".
The ntp package contains such a daemon - indeed, until systemd, almost
certainly the primary such daemon.
The chrony package provi
On 2015-07-26 15:27:50 -0500, John Hasler wrote:
> Vincent Lefevre writes:
> > I want to be able to set the time if for some reason the clock is
> > completely incorrect (this occurred from time to time in the past).
>
> Use your wristwatch.
This may be too late. The mach
On Sun, 26 Jul 2015 15:27:50 -0500
John Hasler wrote:
> > I want to be able to set the time if for some reason the clock is
> > completely incorrect (this occurred from time to time in the past).
>
> Use your wristwatch.
Or better, your cellphone or GPS receive
Vincent Lefevre writes:
> I want to be able to set the time if for some reason the clock is
> completely incorrect (this occurred from time to time in the past).
Use your wristwatch.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-use
hat the authentication system is Autokey, but see above.
> > Even without it, though, sucessfully spoofing all four of the servers
> > you use would be challenging.
>
> > I don't see why this would be difficult for someone who controls the
> > local network (e.g. the wifi
On 2015-07-26 14:45:57 +0100, Brian wrote:
> On Sun 26 Jul 2015 at 15:39:48 +0200, Vincent Lefevre wrote:
> > IMHO, it is bad to be forced to uninstall a package just to make
> > some other package work.
>
> Like not being able to have postfix/exim4 and cups/lprng on a machine at
> the same time,
Gary Dale writes:
> I haven't had any significant problems with systemd but then I waited
> several months before upgrading my servers to jessie and before
> upgrading my workstation to stretch. Maybe it's because of MS-DO but
> I've learned to wait for the .1 release before upgrading. :)
I actu
On 26/07/15 12:47 PM, Dennis Wicks wrote:
Paul E Condon wrote on 07/26/2015 10:14 AM:
On 20150726_0252-0700, anxious...@gmail.com wrote:
Also years ago, and still today, there is approx which does a much
more sophisticated analysis of the data stream of repeated queries of
an ntp server. In
Paul E Condon wrote on 07/26/2015 10:14 AM:
On 20150726_0252-0700, anxious...@gmail.com wrote:
Also years ago, and still today, there is approx which does a much
more sophisticated analysis of the data stream of repeated queries of
an ntp server. In addition to setting the local clock to the
On 26/07/15 10:45 AM, John Hasler wrote:
It may have been an X-Y question, but the answer to the question
actually asked, was "ntp".
That is *an* answer. The full answer is that the Chrony and Ntp
packages provide time daemons. Systemd-timesyncd provides an SNTP
client which is probably adequa
On 26/07/15 08:57 AM, Lisi Reisz wrote:
On Sunday 26 July 2015 13:17:02 Renaud OLGIATI wrote:
On Sun, 26 Jul 2015 10:54:35 +0100
Lisi Reisz wrote:
But that is for wheezy and earlier. systemd is, of course, different.
Maybe the list should implement a rule, that people asking a question tel
Sven Hartge wrote:
>> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
> That one is not present in Sid.
Ah, -ENOCOFFEE, I meant of course "That one is not present in Jessie."
S°
--
Sigmentation fault. Core dumped.
--
To UNSUBSCRIBE, email to debian-user-requ.
L'octidi 8 thermidor, an CCXXIII, Paul E Condon a écrit :
> Also years ago, and still today, there is chrony which does a much
> more sophisticated analysis of the data stream of repeated queries of
> an ntp server. In addition to setting the local clock to the
> same time as the external reference
Paul E Condon writes:
> Also years ago, and still today, there is approx which does a much
> more sophisticated analysis of the data stream of repeated queries of
> an ntp server. In addition to setting the local clock to the same time
> as the external reference clock as is done by both ntp and nt
REPLACE approx with chrony in the following;
> Also years ago, and still today, there is approx which does a much
> more sophisticated analysis of the data stream of repeated queries of
> an ntp server. In addition to setting the local clock to the
> same time as the external reference clock as is
On 20150726_0252-0700, anxious...@gmail.com wrote:
> On Sunday, 26 July 2015 05:30:04 UTC+1, CaT wrote:
> > On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
> > > It is, once ntpdate has slammed the correct time into the system at boot
> > > time, then ntp takes over.
> >
> > Unless
n without it, though, sucessfully spoofing all four of the servers
> you use would be challenging.
> I don't see why this would be difficult for someone who controls the
> local network (e.g. the wifi hotspot).
If your laptop needs precise time and you are a target for such attacks
tak
On Sunday 26 July 2015 15:14:03 Michael Biebl wrote:
> Am 26.07.2015 um 14:57 schrieb Lisi Reisz:
> > Yes, on my one systemd box, I had a problem with which no-one could help
> > me.
> >
> > I do not allege that systemd directly caused it, but that the advent of
> > systemd caused a lot that had wo
> It may have been an X-Y question, but the answer to the question
> actually asked, was "ntp".
That is *an* answer. The full answer is that the Chrony and Ntp
packages provide time daemons. Systemd-timesyncd provides an SNTP
client which is probably adequate for most users.
--
John Hasler
jha
Systemd-timesyncd is not a replacement for Ntpd or Chrony. It is just
an SNTP client similar to that used by Microsoft. It queries a single
server and does no error checking or authentication. Basically, it
replaces a cron job running Ntpdate.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
Am 26.07.2015 um 14:57 schrieb Lisi Reisz:
> Yes, on my one systemd box, I had a problem with which no-one could help me.
>
> I do not allege that systemd directly caused it, but that the advent of
> systemd caused a lot that had worked one way before, to have to work
> differently now; that th
Am 26.07.2015 um 15:39 schrieb Vincent Lefevre:
> On 2015-07-26 14:25:20 +0100, Brian wrote:
>> On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
>>> On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
Yes. You actually need to do that. As long as ntp is installed,
systemd-tim
On Sunday 26 July 2015 14:52:56 Bob Bernstein wrote:
> Another reason why
> the correct answer to the OP's question is NOT "ntp."
The question was:
"What package contains the time daemon?"
It may have been an X-Y question, but the answer to the question ac
On Sun, 26 Jul 2015, Michael Biebl wrote:
Yes. You actually need to do that. As long as ntp is
installed, systemd-timesyncd won't start.
I'd like to suggest that if I were a vindictive,
morally shallow person I would be rushing back into
this thread to point out: "Oh look! Another reason why
On Sun 26 Jul 2015 at 15:39:48 +0200, Vincent Lefevre wrote:
> On 2015-07-26 14:25:20 +0100, Brian wrote:
> > On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
> > > On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
> > > >
> > > > Yes. You actually need to do that. As long as ntp is inst
On 2015-07-26 14:25:20 +0100, Brian wrote:
> On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
> > On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
> > >
> > > Yes. You actually need to do that. As long as ntp is installed,
> > > systemd-timesyncd won't start.
> > > The assumption here is
On Sun 26 Jul 2015 at 13:59:02 +0100, Lisi Reisz wrote:
> On Sunday 26 July 2015 13:38:45 Michael Biebl wrote:
> >
> > Yes. You actually need to do that. As long as ntp is installed,
> > systemd-timesyncd won't start.
> > The assumption here is, that if the admin explicitly installed ntp, it
> > s
On Sun 26 Jul 2015 at 14:57:02 +0200, Sven Hartge wrote:
> Michael Biebl wrote:
>
> > The assumption here is, that if the admin explicitly installed ntp, it
> > should be preferred of systemd-timesyncd.
> > See
>
> > /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
On 2015-07-26 07:53:45 -0500, John Hasler wrote:
> Vincent Lefevre writes:
> > Unfortunately none of them is secure, I mean: some attacker won't tend
> > to make the date on your machine incorrect because of lack of
> > authentication.
>
> http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm
>
> See se
On Sun, Jul 26, 2015 at 02:38:45PM +0200, Michael Biebl wrote:
> Am 26.07.2015 um 13:44 schrieb Chris Bannister:
> > On Sun, Jul 26, 2015 at 02:03:48AM +0200, Michael Biebl wrote:
> >>>
> >>> If you are using systemd, look for timedatectl. Settings are at
> >>> /etc/systemd/timesyncd.conf
> >>
> >>
wondering if my Jessie system is updating its clock
>>>>> regularly. It gives a different time than my Windows box. What
>>>>> package contains the daemon that updates the time from a central
>>>>> site?
[...]
>> I think that answers my other
oyer:
> >>>> I am wondering if my Jessie system is updating its clock regularly. It
> >>>> gives a
> >>>> different time than my Windows box. What package contains the daemon
> >>>> that updates the time from a central site?
>
On Sunday 26 July 2015 13:17:02 Renaud OLGIATI wrote:
> On Sun, 26 Jul 2015 10:54:35 +0100
>
> Lisi Reisz wrote:
> > But that is for wheezy and earlier. systemd is, of course, different.
>
> Maybe the list should implement a rule, that people asking a question tell
> us whether they are running
Vincent Lefevre writes:
> Unfortunately none of them is secure, I mean: some attacker won't tend
> to make the date on your machine incorrect because of lack of
> authentication.
http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm
See section 6.6.2, Authentication
Even without it, though, sucessfully
dating its clock regularly. It
>>>> gives a
>>>> different time than my Windows box. What package contains the daemon
>>>> that updates the time from a central site?
>>>
>>> If you are using systemd, look for timedatectl. Settings are at
>>&
On Sun, 26 Jul 2015 10:54:35 +0100
Lisi Reisz wrote:
> But that is for wheezy and earlier. systemd is, of course, different.
Maybe the list should implement a rule, that people asking a question tell us
whether they are running systemd or not.
Given that the advent of systemd has, as a stroke
anxiousmac writes:
> Years ago ... we didn't all have always-on connections.
Chrony was developed to solve that problem.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
CaT writes:
> Unless I misremember, you don't even need ntpdate. Starting ntp with
> -g will do just fine (and it's the default config - I add -N). I don't
> even have ntpdate installed.
Yes. Ntpdate is obsolete.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to d
On 2015-07-26 02:31:45 +0200, Michael Biebl wrote:
> You can have a client, which is a daemon.
> ntp implements both, an NTP client and server.
> systemd-timesyncd only implements a client (running as daemon).
> chrony, fwiw, is another client (running as daemon).
> ntpdate is a client (triggered v
erent time than my Windows box. What package contains the daemon
> >> that updates the time from a central site?
> >
> > If you are using systemd, look for timedatectl. Settings are at
> > /etc/systemd/timesyncd.conf
>
> In most cases, simply running "
On Sun, Jul 26, 2015 at 10:54:35AM +0100, Lisi Reisz wrote:
> On Sunday 26 July 2015 05:09:37 CaT wrote:
> > On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
> > > It is, once ntpdate has slammed the correct time into the system at boot
> > > time, then ntp takes over.
> >
> > Unless I
On Sunday, 26 July 2015 05:30:04 UTC+1, CaT wrote:
> On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
> > It is, once ntpdate has slammed the correct time into the system at boot
> > time, then ntp takes over.
>
> Unless I misremember, you don't even need ntpdate. Starting ntp with
On Sunday 26 July 2015 05:09:37 CaT wrote:
> On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
> > It is, once ntpdate has slammed the correct time into the system at boot
> > time, then ntp takes over.
>
> Unless I misremember, you don't even need ntpdate. Starting ntp with
> -g will d
On Sat, Jul 25, 2015 at 11:32:53PM -0400, Gene Heskett wrote:
> It is, once ntpdate has slammed the correct time into the system at boot
> time, then ntp takes over.
Unless I misremember, you don't even need ntpdate. Starting ntp with
-g will do just fine (and it's the default config - I add -N).
gt; question. Since ntpdate does not depend on ntp, then I
> have to say, simply REALLY!
But ntpdate is only used at bootup, once. The machine can and will drift.
Running ntp as a daemon, it checks the round trip time and initially
adjusts the time to within a few milliseconds of NBS time, tr
The Wanderer writes:
> The original question was "What package contains the daemon that
> updates the time from a central site?".
> The ntp package contains such a daemon - indeed, until systemd, almost
> certainly the primary such daemon.
The chrony package provides a tim
On Sat, 25 Jul 2015, The Wanderer wrote:
This is bordering on code-of-conduct
questionability.
I'm glad to hear that. I can see that my work here is
done.
--
I am not a loony. Why should I be tarred with the epithet
'loony' merely because I have a pet halibut? I've heard
tell that Sir Ge
Am 26.07.2015 um 02:23 schrieb The Wanderer:
> The original question was "What package contains the daemon that updates
> the time from a central site?".
>
> The ntp package contains such a daemon - indeed, until systemd, almost
> certainly the primary such daemon. (And
suggested that was the be-all and end-all of the
> question. I have run out of patience with the self-appointed experts
> on this list who are clearly suffering from delusions of adequacy, if
> not outright IQ insufficiency.
Chill, dude. This is bordering on code-of-conduct questionability.
On Sun, 26 Jul 2015, Iain M Conochie wrote:
No. This is an incorrect response.
Really?
Um...your own homework, below, suggests that ntp is
not the only package that performs the task in
question. Since ntpdate does not depend on ntp, then I
have to say, simply REALLY!
apt-cache search
Am 25.07.2015 um 21:26 schrieb Holger Schramm:
> Am 25.07.2015 um 20:52 schrieb John J. Boyer:
>> I am wondering if my Jessie system is updating its clock regularly. It
>> gives a
>> different time than my Windows box. What package contains the daemon
>> that upda
On Sat, 25 Jul 2015 19:08:33 -0400 (EDT)
Bob Bernstein wrote:
> On Sat, 25 Jul 2015, Gary Dale wrote:
> > ntp
> No. This is an incorrect response.
According to the Description of the package ntp:
"This package contains the NTP daemon and utility programs. "
Cheers,
Ron.
--
La perfec
On 26/07/15 00:08, Bob Bernstein wrote:
On Sat, 25 Jul 2015, Gary Dale wrote:
ntp
No. This is an incorrect response.
Really?
apt-cache search ntp | grep ^ntp
ntp - Network Time Protocol daemon and utility programs
ntp-doc - Network Time Protocol documentation
ntpdate - client for settin
1 - 100 of 251 matches
Mail list logo
