Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #258316 > unrolled thread

No space left on device ...

Back to article view | Back to linux.debian.user

Contents

  No space left on device ... Albretch Mueller <lbrtchx@gmail.com> - 2023-05-15 02:40 +0200
    Re: No space left on device ... Jeffrey Walton <noloader@gmail.com> - 2023-05-15 03:10 +0200
      Re: No space left on device ... Joe <joe@jretrading.com> - 2023-05-15 09:40 +0200
        Re: No space left on device ... Klaus Singvogel <deb-user-ml@singvogel.net> - 2023-05-15 11:10 +0200
    Re: No space left on device ... Charles Curley <charlescurley@charlescurley.com> - 2023-05-15 05:20 +0200
    Re: No space left on device ... Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-05-15 12:00 +0200
      Re: No space left on device ... Albretch Mueller <lbrtchx@gmail.com> - 2023-05-16 04:10 +0200
        Re: No space left on device ... Albretch Mueller <lbrtchx@gmail.com> - 2023-05-17 18:50 +0200
          Re: No space left on device ... Dan Ritter <dsr@randomstring.org> - 2023-05-17 19:10 +0200
            Re: No space left on device ... Jeffrey Walton <noloader@gmail.com> - 2023-05-17 19:20 +0200
              Re: No space left on device ... Albretch Mueller <lbrtchx@gmail.com> - 2023-05-20 10:20 +0200
                Re: No space left on device ... "Andrew M.A. Cater" <amacater@einval.com> - 2023-05-20 12:10 +0200
            Re: No space left on device ... Charles Curley <charlescurley@charlescurley.com> - 2023-05-17 21:50 +0200
              Re: No space left on device ... Default User <hunguponcontent@gmail.com> - 2023-05-18 16:10 +0200
                Re: No space left on device ... Dan Ritter <dsr@randomstring.org> - 2023-05-18 16:40 +0200
                  Re: No space left on device ... Default User <hunguponcontent@gmail.com> - 2023-05-18 17:30 +0200
                Re: No space left on device ... Charles Curley <charlescurley@charlescurley.com> - 2023-05-18 18:50 +0200
                  Re: No space left on device ... Default User <hunguponcontent@gmail.com> - 2023-05-18 21:40 +0200

#258316 — No space left on device ...

I have been mounting an NTFS file system on a Windows laptop without
any problems whatsoever with a Debian Live DVD:

$ uname -a
Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02)
x86_64 GNU/Linux

and even though Linux utilities are telling me I do have space on the drive:

$ date; sudo df -h | grep "Filesystem\|/dev/sd"
Sun 14 May 2023 06:55:23 PM UTC
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       286G  167G  120G  59% /media/user/60320G593EB7250F
$

$ date; time sudo du --summarize --human-readable  /media/user/60320G593EB7250F
Sun 14 May 2023 07:13:43 PM UTC
166G	/media/user/60320G593EB7250F

real	0m45.230s
user	0m1.073s
sys	0m15.443s
$

when I try to save or download a file I consistently get the same error message:

$ cp "No space left on device" > No_space_left_on_device.txt
bash: No_space_left_on_device.txt: No space left on device

that started happening right after a WiFi connection at a library was
shutdown, which I waited for with my script running, accessing the
Internet, because I wanted to test such a case. Script "gracefully"
worked as programmed to do, but that other error started right after
the connection was cut off.

I have no idea how could those two things be related! Why would that
happen? Any suggestions, please?

lbrtchx

[toc] | [next] | [standalone]

#258318

On Sun, May 14, 2023 at 8:32 PM Albretch Mueller <lbrtchx@gmail.com> wrote:
>
> I have been mounting an NTFS file system on a Windows laptop without
> any problems whatsoever with a Debian Live DVD:
>
> $ uname -a
> Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02)
> x86_64 GNU/Linux
>
> and even though Linux utilities are telling me I do have space on the drive:
>
> $ date; sudo df -h | grep "Filesystem\|/dev/sd"
> Sun 14 May 2023 06:55:23 PM UTC
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/sda1       286G  167G  120G  59% /media/user/60320G593EB7250F
> $
>
> $ date; time sudo du --summarize --human-readable  /media/user/60320G593EB7250F
> Sun 14 May 2023 07:13:43 PM UTC
> 166G    /media/user/60320G593EB7250F
>
> real    0m45.230s
> user    0m1.073s
> sys     0m15.443s
> $
>
> when I try to save or download a file I consistently get the same error message:
>
> $ cp "No space left on device" > No_space_left_on_device.txt
> bash: No_space_left_on_device.txt: No space left on device
>
> that started happening right after a WiFi connection at a library was
> shutdown, which I waited for with my script running, accessing the
> Internet, because I wanted to test such a case. Script "gracefully"
> worked as programmed to do, but that other error started right after
> the connection was cut off.
>
> I have no idea how could those two things be related! Why would that
> happen? Any suggestions, please?

I don't know if it's related...

I seem to recall the GNUlib folks talking about a cp bug on sparse
files. It looks like it may be fixed in coreutils release 9.2
(2023-03-20): https://github.com/coreutils/coreutils/blob/master/NEWS#L233

If I recall correctly, it had something to do with the way
copy_file_range worked. (Or maybe, it did not work as expected).

Jeff

[toc] | [prev] | [next] | [standalone]

#258331

On Sun, 14 May 2023 21:04:01 -0400
Jeffrey Walton <noloader@gmail.com> wrote:

> On Sun, May 14, 2023 at 8:32 PM Albretch Mueller <lbrtchx@gmail.com>
> wrote:
> >
> > I have been mounting an NTFS file system on a Windows laptop without
> > any problems whatsoever with a Debian Live DVD:
> >
> > $ uname -a
> > Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02)
> > x86_64 GNU/Linux
> >
> > and even though Linux utilities are telling me I do have space on
> > the drive:
> >
> > $ date; sudo df -h | grep "Filesystem\|/dev/sd"
> > Sun 14 May 2023 06:55:23 PM UTC
> > Filesystem      Size  Used Avail Use% Mounted on
> > /dev/sda1       286G  167G  120G  59% /media/user/60320G593EB7250F
> > $
> >
> > $ date; time sudo du --summarize --human-readable
> > /media/user/60320G593EB7250F Sun 14 May 2023 07:13:43 PM UTC
> > 166G    /media/user/60320G593EB7250F
> >
> > real    0m45.230s
> > user    0m1.073s
> > sys     0m15.443s
> > $
> >
> > when I try to save or download a file I consistently get the same
> > error message:
> >
> > $ cp "No space left on device" > No_space_left_on_device.txt
> > bash: No_space_left_on_device.txt: No space left on device
> >
> > that started happening right after a WiFi connection at a library
> > was shutdown, which I waited for with my script running, accessing
> > the Internet, because I wanted to test such a case. Script
> > "gracefully" worked as programmed to do, but that other error
> > started right after the connection was cut off.
> >
> > I have no idea how could those two things be related! Why would that
> > happen? Any suggestions, please?  
> 
> I don't know if it's related...
> 
> I seem to recall the GNUlib folks talking about a cp bug on sparse
> files. It looks like it may be fixed in coreutils release 9.2
> (2023-03-20):
> https://github.com/coreutils/coreutils/blob/master/NEWS#L233
> 
> If I recall correctly, it had something to do with the way
> copy_file_range worked. (Or maybe, it did not work as expected).
> 

First thing to try is to boot back into Windows and see if there is a
message about the drive. If so, let Windows 'fix' it. I've had cases
where the drive was not cleanly unmounted and Linux has mounted it
read-only. Windows was able to repair it, whatever the problem was.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#258338

Joe wrote:
> 
> First thing to try is to boot back into Windows and see if there is a
> message about the drive. If so, let Windows 'fix' it. I've had cases
> where the drive was not cleanly unmounted and Linux has mounted it
> read-only. Windows was able to repair it, whatever the problem was.

Oh! Reminds me on the fact, that Fast Boot of Windows locks the disk devices,
and they can't be accessed by any other system on the same computer, even after
Windows shutdown - to avoid disk corruption.

Did you disable the Fast Boot feature in Windows?

https://www.howtogeek.com/243901/the-pros-and-cons-of-windows-10s-fast-startup-mode/

Best regards,
	Klaus.


-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

[toc] | [prev] | [next] | [standalone]

#258325

On Mon, 15 May 2023 00:32:01 +0000
Albretch Mueller <lbrtchx@gmail.com> wrote:

> when I try to save or download a file I consistently get the same
> error message:
> 
> $ cp "No space left on device" > No_space_left_on_device.txt
> bash: No_space_left_on_device.txt: No space left on device

That *shouldn't* work. I get:

charles@jhegaala:~$ cp "No space left on device" > No_space_left_on_device.txt
cp: missing destination file operand after 'No space left on device'
Try 'cp --help' for more information.
charles@jhegaala:~$ 

But I do get a file created with length 0.

Try echo instead of cp:

charles@jhegaala:~$ echo "No space left on device" > No_space_left_on_device.txt
charles@jhegaala:~$ cat No_space_left_on_device.txt 
No space left on device
charles@jhegaala:~$ ll No_space_left_on_device.txt 
-rw-r--r-- 1 charles charles 24 May 14 21:04 No_space_left_on_device.txt
charles@jhegaala:~$ 

Also, I have no reason to believe from what you've shown that your
current directory is /media/user/60320G593EB7250F. Did you run

cd /media/user/60320G593EB7250F

before running the above commands? I would expect to get an
out-of-space error if I were still on the CD.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#258339

Albretch Mueller <lbrtchx@gmail.com> writes:

> I have been mounting an NTFS file system on a Windows laptop without
> any problems whatsoever with a Debian Live DVD:

Mounting how exactly? And what is the contents of /proc/mounts? Maybe
you mounted the partition read only?

[toc] | [prev] | [next] | [standalone]

#258403

> Has this ever worked in the past? It is my understanding that the Linux NTFS driver is read-only.
> Mounting how exactly? And what is the contents of /proc/mounts? Maybe
> you mounted the partition read only?

 Well, actually, yes. This is how I have been mounting the Windows
NTFS of my laptop and my employer's as well without any problems
whatsoever. I just open the file browser/viewer and click the drive to
mount it in order to unmount, eject it you right click on it. It
works.

>> $ cp "No space left on device" > No_space_left_on_device.txt
>> bash: No_space_left_on_device.txt: No space left on device

>That *shouldn't* work. I get:

 my mistake I meant: echo "No space left on device" >
No_space_left_on_device.txt

> Does anybody read signatures any more?

 Apparently, some of us do. ;-) My obfuscation of the path didn't
relate to the error.

> First thing to try is to boot back into Windows and see if there is a
message about the drive. If so, let Windows 'fix' it. I've had cases
where the drive was not cleanly unmounted and Linux has mounted it
read-only. Windows was able to repair it, whatever the problem was.

 THis is the second thing I did. I booted into the BIOS and run an
exhaustive test/diagnostic on every physical part of it twice. It all
tested fine, including the hard drive.

 Then something spooky happened. I couldn't care less about Windows,
but then "'the BIOS' 'told me'" it would fix my laptop and it effing
did without messing with any of my data!!! Then I could boot into
windows again ... once I checked everything was fine I went back to my
Debian live ways.

 Every electronic thing I use has a mind of its own, that makes your
life so much more enjoyable! ;-)

> Did you disable the Fast Boot feature in Windows?

 Yes, I did. I had to reset the BIOS to "factory settings" which also
changed the clock time which then I couldn't change with hwclock ...
but when I booted the laptop with a network access at the library. It
did reset the clock apparently using WIndows time servers.

 That fix took me like four hours (dealing with the nonsense of the
installation ...), but at the end of th eday I was able to go back to
my do, do, do, ... mode.

 Thank you,
 lbrtchx

[toc] | [prev] | [next] | [standalone]

#258465

> Yes, I did. I had to reset the BIOS to "factory settings" which also
> changed the clock time which then I couldn't change with hwclock ...

 "Another day another problem": computer clock back to BIOS factory settings

 Your Computer Clock is Wrong:
 Your computer thinks it is 8/7/2022, which prevents Firefox from
connecting securely. To visit www.google.com, update your computer
clock in your system settings to the current date, time, and time
zone, and then refresh www.google.com.
 www.google.com has a security policy called HTTP Strict Transport
Security (HSTS), which means that Firefox can only connect to it
securely. You can’t add an exception to visit this site.
~
 In case someone runs into the same problem, for some reason I can't
quite understand "sudo hwclock --set" wasn't working. Someone helped
me:

 https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html
 https://wiki.debian.org/DateTime

 and "date" worked! Which I has always taken to be a wrapper command to hwclock!

$ date
Sun 07 Aug 2022 01:35:45 PM UTC

$ sudo date --set "2023-05-16 11:13:00 AM"
Tue 16 May 2023 11:13:00 AM UTC

$ sudo hwclock --get
2022-05-11 02:02:36.883165+00:00

$ sudo hwclock --systohc

$ sudo hwclock --get
2023-05-16 11:15:22.564093+00:00

 "Amazing!"
 lbrtchx

[toc] | [prev] | [next] | [standalone]

#258467

Albretch Mueller wrote: 
>  In case someone runs into the same problem, for some reason I can't
> quite understand "sudo hwclock --set" wasn't working. Someone helped
> me:
> 
>  https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html
>  https://wiki.debian.org/DateTime
> 
>  and "date" worked! Which I has always taken to be a wrapper command to hwclock!
> 
> $ date
> Sun 07 Aug 2022 01:35:45 PM UTC
> 
> $ sudo date --set "2023-05-16 11:13:00 AM"
> Tue 16 May 2023 11:13:00 AM UTC
> 
> $ sudo hwclock --get
> 2022-05-11 02:02:36.883165+00:00
> 
> $ sudo hwclock --systohc
> 
> $ sudo hwclock --get
> 2023-05-16 11:15:22.564093+00:00

Assuming you have network access close to boot time, you might
want to run an NTP daemon to get the time from a selection of
other servers.

Debian runs a pool, which is configured by default in ntp-server
and chrony, at least.

-dsr-

[toc] | [prev] | [next] | [standalone]

#258468

On Wed, May 17, 2023 at 1:06 PM Dan Ritter <dsr@randomstring.org> wrote:
>
> Albretch Mueller wrote:
> >  In case someone runs into the same problem, for some reason I can't
> > quite understand "sudo hwclock --set" wasn't working. Someone helped
> > me:
> >
> >  https://manpages.debian.org/stretch/util-linux/hwclock.8.en.html
> >  https://wiki.debian.org/DateTime
> >
> >  and "date" worked! Which I has always taken to be a wrapper command to hwclock!
> >
> > $ date
> > Sun 07 Aug 2022 01:35:45 PM UTC
> >
> > $ sudo date --set "2023-05-16 11:13:00 AM"
> > Tue 16 May 2023 11:13:00 AM UTC
> >
> > $ sudo hwclock --get
> > 2022-05-11 02:02:36.883165+00:00
> >
> > $ sudo hwclock --systohc
> >
> > $ sudo hwclock --get
> > 2023-05-16 11:15:22.564093+00:00
>
> Assuming you have network access close to boot time, you might
> want to run an NTP daemon to get the time from a selection of
> other servers.

++. Let the software handle it.

Nowadays, time is something that can be handled locally with a Gossip
protocol. Let your watch or phone or television or toaster tell your
computer what time it is. No need for a remote call to a server.

> Debian runs a pool, which is configured by default in ntp-server
> and chrony, at least.

Jeff

[toc] | [prev] | [next] | [standalone]

#258530

On 5/17/23, Jeffrey Walton <noloader@gmail.com> wrote:
> On Wed, May 17, 2023 at 1:06 PM Dan Ritter <dsr@randomstring.org> wrote:
>> Albretch Mueller wrote:
>> Assuming you have network access close to boot time, you might
>> want to run an NTP daemon to get the time from a selection of
>> other servers.
> Nowadays, time is something that can be handled locally with a Gossip
> protocol. Let your watch or phone or television or toaster tell your
> computer what time it is. No need for a remote call to a server.
>
>> Debian runs a pool, which is configured by default in ntp-server
>> and chrony, at least.

 I have to use a Debian Live DVD to access the Internet; so, probably
these utilities should be included. I can't entertain functional
illusions about taking care of my business in any other way. It is
thoroughly annoying and time wasting, but you also "live and learn". I
have been running dmesg and comparing its output as I access the
Internet (all problems go away when you close all browser windows and
disconnect yourself from the Internet) one of their jokes is making
the hard drive crazily rev and then you find the message:

 [70778.162999] Thunar[1669]: segfault at 48 ip 000055a03faca360 sp
00007ffc52dc2088 error 4 in thunar[55a03fa9f000+7f000]

 When our AI-based "Miss Information" Godmother gets angry with you ;-)

 They are even able to change BIOS settings while your computer is
running through your browser!

// __ List BIOS Settings using PowerShell (Posted onJune 22, 2016AuthorMrNetTek)

 http://eddiejackson.net/wp/?p=10909
~
 so, at some point I will have to get diffable dumps of the BIOS in
addition to running diffing the output of dmesg.

 The main problems I am having are brought about by:

 1) the BIOS of the laptop I use these days having wireless networking
which is started by the BIOS (at some point I will try dealing with
that by disconnecting the built-in hardware). In the ways I understand
"reality" (and "quid est verum?", right?) the BIOS should not be
taking care of networking, "have a mind of its own";

 2) javascript is the main attacking framework used by "the
government" and how can you use the Internet these days with
javascript disabled? (it would be like trying to breathe underwater)

 3) "the government" is using AI for their societally-wide
Zersetzung-like "social control" (as "good Christian" "freedom lovers"
call -repression-)

 How do I know, am so sure about it? Well, this is a pattern that I
have been noticing for 30 years I have lived in "'the' land of 'the'
'free' ...": you post an "unAmerican" comment (here in the U.S. you
can say "eff 'the establishment' ..." and no one cares about it, in
fact, you didn't say anything even in a physical/acoustic sense, but
in a "lexical priming" kind of way, if you elaborate on your
statements even if in a jestful way, "patriots"/their "'patriotic'
'AI'" seem to go crazy about it).

 This is what happened last/this time: you notice the people you get
the news from (I don't watch TV, read newspapers, nor am I on social
networks, ... in fact, I wonder from where people find the time for
such thoroughly stupid, morally debasing pastimes) have been black
holed -again-, to then after some barely sophisticated be found here:

// __ Introducing: Miss Information, Your Fairy Government Godmother

 https://odysee.com/@Odysee:8/missinfo:d
~
 About our new Godmother "Miss Information". Do you remember when she
decided it was about time for "Vladimir Putin" to suicide Michael
Hastings for spreading misinformation?

 https://en.wikipedia.org/wiki/Michael_Hastings_(journalist)

 Two days after the crash, the Los Angeles Police Department declared
that there were no signs of foul play.[65] The coroner's report ruled
the death to be an accident.[66] An autopsy showed that the cause of
death was massive blunt force trauma consistent with a high-speed
crash.[66]
~
 I cracked jokes around how unjust and non-sensical was it that that
not only "unAmerican", but also, as if it were not enough, "pro
Russia" "Vladimir Putin" suicided Hastings when all he did was the
same as Biden did only 20 years earlier. Do we need either "Vladimir
Putin" or our, not exactly fair and clarifying government appointed
Godmother?
~
 The aim of that Zersetzung-like (as they "freedom-lovingly" call it
themselves: "relentless pursuit"), which was thoroughly "studied" with
social animals and humans as part of their „Operativer Vorgänge"
("operational procedures") by the East German stasi is not to kill
you, but thoroughly destroy your existence to the point of inducing
the belief in people of committing suicide as a way "not to let them
get you" ... Does it actually work? Well, you don't have to take it
from me; Ian Murdock, Aaron Swartz, Sandra Bland, Myron May, John
McAfee, ... will tell you.

 I know, as some of you have told me, that "the U.S. Constitution
doesn't include any clauses relating to 'privacy'" ..., that "all I am
saying is being archived" ... (yes, "we the people" in the U.S. have
started to talk as if they were telling Soviet-era jokes, very
unfortunately, they have a compromised sense of humor)

 lbrtchx

[toc] | [prev] | [next] | [standalone]

#258533

On Sat, May 20, 2023 at 08:12:39AM +0000, Albretch Mueller wrote:
> On 5/17/23, Jeffrey Walton <noloader@gmail.com> wrote:
> > On Wed, May 17, 2023 at 1:06 PM Dan Ritter <dsr@randomstring.org> wrote:
> >> Albretch Mueller wrote:
> >> Assuming you have network access close to boot time, you might
> >> want to run an NTP daemon to get the time from a selection of
> >> other servers.
> > Nowadays, time is something that can be handled locally with a Gossip
> > protocol. Let your watch or phone or television or toaster tell your
> > computer what time it is. No need for a remote call to a server.
> >
> >> Debian runs a pool, which is configured by default in ntp-server
> >> and chrony, at least.
> 
>  I have to use a Debian Live DVD to access the Internet; so, probably
> these utilities should be included. 
> 
>  lbrtchx
> 

Hi,

Most of this message from you is very off topic: please bear in mind
that this goes to a *wide* variety of people and places. That's one
of the reasons why the FAQ posted each month asks people to not post
political and other opinions that may be meaningless to large parts
of the world.

Can we try and get this list back onto topics that are constructive
(and don't last for thirty or more posts in one thread), please?

Thanks for your consideration.

Andy Cater
[For the Debian Community Team]

[toc] | [prev] | [next] | [standalone]

#258473

On Wed, 17 May 2023 12:48:28 -0400
Dan Ritter <dsr@randomstring.org> wrote:

> Assuming you have network access close to boot time, you might
> want to run an NTP daemon to get the time from a selection of
> other servers.

Concur.

> 
> Debian runs a pool, which is configured by default in ntp-server
> and chrony, at least.

Also systemd-timesyncd, which is probably the easiest of these three to
set up.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#258496

On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote:
> On Wed, 17 May 2023 12:48:28 -0400
> Dan Ritter <dsr@randomstring.org> wrote:
> 
> > Assuming you have network access close to boot time, you might
> > want to run an NTP daemon to get the time from a selection of
> > other servers.
> 
> Concur.
> 
> > 
> > Debian runs a pool, which is configured by default in ntp-server
> > and chrony, at least.
> 
> Also systemd-timesyncd, which is probably the easiest of these three
> to
> set up.
> 
> 


If I am running systemd-timesyncd on a single-user, internet-connected
computer, not needing to serve time signals to any other device, would
there be any reason to use ntp instead?

[INB4: "If it ain't broke, don't fix it!"]

:)

[toc] | [prev] | [next] | [standalone]

#258499

Default User wrote: 
> On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote:
> > On Wed, 17 May 2023 12:48:28 -0400
> > Dan Ritter <dsr@randomstring.org> wrote:
> > 
> > > Assuming you have network access close to boot time, you might
> > > want to run an NTP daemon to get the time from a selection of
> > > other servers.
> > 
> > Concur.
> > 
> > > 
> > > Debian runs a pool, which is configured by default in ntp-server
> > > and chrony, at least.
> > 
> > Also systemd-timesyncd, which is probably the easiest of these three
> > to
> > set up.
> > 
> > 
> 
> 
> If I am running systemd-timesyncd on a single-user, internet-connected
> computer, not needing to serve time signals to any other device, would
> there be any reason to use ntp instead?

systemd-timesyncd, ntp-server and chrony are all supposed to
speak the NTP protocol. Nothing, to a first approximation, uses
any other protocol to set time reliably for the system as a
whole.

-dsr-

[toc] | [prev] | [next] | [standalone]

#258500

On Thu, 2023-05-18 at 10:20 -0400, Dan Ritter wrote:
> Default User wrote: 
> > On Wed, 2023-05-17 at 13:48 -0600, Charles Curley wrote:
> > > On Wed, 17 May 2023 12:48:28 -0400
> > > Dan Ritter <dsr@randomstring.org> wrote:
> > > 
> > > > Assuming you have network access close to boot time, you might
> > > > want to run an NTP daemon to get the time from a selection of
> > > > other servers.
> > > 
> > > Concur.
> > > 
> > > > 
> > > > Debian runs a pool, which is configured by default in ntp-
> > > > server
> > > > and chrony, at least.
> > > 
> > > Also systemd-timesyncd, which is probably the easiest of these
> > > three
> > > to
> > > set up.
> > > 
> > > 
> > 
> > 
> > If I am running systemd-timesyncd on a single-user, internet-
> > connected
> > computer, not needing to serve time signals to any other device,
> > would
> > there be any reason to use ntp instead?
> 
> systemd-timesyncd, ntp-server and chrony are all supposed to
> speak the NTP protocol. Nothing, to a first approximation, uses
> any other protocol to set time reliably for the system as a
> whole.
> 
> -dsr-



Okay, thanks!

[toc] | [prev] | [next] | [standalone]

#258501

On Thu, 18 May 2023 10:07:05 -0400
Default User <hunguponcontent@gmail.com> wrote:

> If I am running systemd-timesyncd on a single-user, internet-connected
> computer, not needing to serve time signals to any other device, would
> there be any reason to use ntp instead?

NTP is a protocol, like TCP or UDP. One program that uses NTP is ntpd,
which Debian packages in the confusingly named package ntp.

To answer your question, probably not. I'm not even sure you can run
ntpd and systemd-timesyncd on the same computer. I have ntpd on two
computers here, both available as local time servers on my network.
Everything else uses systemd-timesyncd and uses the two ntpd machines.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#258505

On Thu, 2023-05-18 at 10:42 -0600, Charles Curley wrote:
> On Thu, 18 May 2023 10:07:05 -0400
> Default User <hunguponcontent@gmail.com> wrote:
> 
> > If I am running systemd-timesyncd on a single-user, internet-
> > connected
> > computer, not needing to serve time signals to any other device,
> > would
> > there be any reason to use ntp instead?
> 
> NTP is a protocol, like TCP or UDP. One program that uses NTP is
> ntpd,
> which Debian packages in the confusingly named package ntp.
> 
> To answer your question, probably not. I'm not even sure you can run
> ntpd and systemd-timesyncd on the same computer. I have ntpd on two
> computers here, both available as local time servers on my network.
> Everything else uses systemd-timesyncd and uses the two ntpd
> machines.
> 


Got it. That's sort of what I was thinking.  
Thanks!

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web