On Tue, Sep 20, 2022 at 7:55 AM Patrick O'Callaghan
wrote:
> On Tue, 2022-09-20 at 20:16 +0930, Tim via users wrote:
> > On Mon, 2022-09-19 at 21:59 -0500, Chris Adams wrote:
> > > Mail servers, on the other hand, were jumping to the file-per-
> > > message
> > > method just as fast as Usenet
On Tue, 2022-09-20 at 20:16 +0930, Tim via users wrote:
> On Mon, 2022-09-19 at 21:59 -0500, Chris Adams wrote:
> > Mail servers, on the other hand, were jumping to the file-per-
> > message
> > method just as fast as Usenet servers discarded it, and are still
> > using
> > it.
>
> I certainly
On Mon, 2022-09-19 at 21:59 -0500, Chris Adams wrote:
> Mail servers, on the other hand, were jumping to the file-per-message
> method just as fast as Usenet servers discarded it, and are still using
> it.
I certainly noticed a massive improvement when I went from mail spool
files to maildir on
On Tue, 2022-09-20 at 01:35 -0400, Jon LaBadie wrote:
> like the time a nimwit admin of a multi-user
> computer (300 users) came home from a security class learning
> that "setuid programs were bad". Over the weekend they used
> chmod to remove the setuid bit of every program on the system.
>
On 20 Sep 2022 at 1:35, Jon LaBadie wrote:
Date sent: Tue, 20 Sep 2022 01:35:02 -0400
From: Jon LaBadie
To: users@lists.fedoraproject.org
Subject:Re: Question on bad links?
Send reply to: Community support for Fedora
On Sat, Sep 17, 2022 at 10:53:53AM -0400, Jonathan Billings wrote:
On Sep 16, 2022, at 20:44, Michael D. Setzer II via users
wrote:
Was not aware of that program? Was already installed on my system. Following
instructions from link, it found 279 of the broken links under /usr and after
On 2022-09-19 16:40, Stephen Morris wrote:
On 19/9/22 11:01, Samuel Sieb wrote:
On 9/18/22 16:44, Stephen Morris wrote:
Just an FYI, I've issued ll /run/systemd/units and on my system
that folder contains nothing but symlinks and everyone of them are
pointing at files that don't exist.
Once upon a time, Robert Nichols said:
> It's a problem that crops up occasionally, and makes people wonder why they
> get a "No space on filesystem" error when the df command shows that plenty of
> space is available. That's why the df command has a "-i" option to report
> inode usage. A
On 9/19/22 3:53 PM, Barry wrote:
On 19 Sep 2022, at 06:30, Tim via users wrote:
On Sun, 2022-09-18 at 21:44 -0500, Robert Nichols wrote:
With a symlink, that "data" is the string that shows as the symlink
target. The advantage over a tiny file is that if the string is short
enough to fit
On 19/9/22 11:01, Samuel Sieb wrote:
On 9/18/22 16:44, Stephen Morris wrote:
Just an FYI, I've issued ll /run/systemd/units and on my system
that folder contains nothing but symlinks and everyone of them are
pointing at files that don't exist. If these are created every boot,
then what
> On 19 Sep 2022, at 06:30, Tim via users wrote:
>
> On Sun, 2022-09-18 at 21:44 -0500, Robert Nichols wrote:
>> With a symlink, that "data" is the string that shows as the symlink
>> target. The advantage over a tiny file is that if the string is short
>> enough to fit within the inode
On 9/19/22 12:29 AM, Tim via users wrote:
On Sun, 2022-09-18 at 21:44 -0500, Robert Nichols wrote:
With a symlink, that "data" is the string that shows as the symlink
target. The advantage over a tiny file is that if the string is short
enough to fit within the inode structure, no data block on
On Sun, 2022-09-18 at 21:44 -0500, Robert Nichols wrote:
> With a symlink, that "data" is the string that shows as the symlink
> target. The advantage over a tiny file is that if the string is short
> enough to fit within the inode structure, no data block on the disk
> needs to be allocated.
On 9/18/22 9:23 PM, Tim via users wrote:
On Sun, 2022-09-18 at 18:01 -0700, Samuel Sieb wrote:
As Jonathan mentioned in a previous reply, systemd is using symlinks for
temporary data storage, like a dictionary or map depending on which
programming language you're using.
Kinda wierd. I wonder
On Sun, 2022-09-18 at 18:01 -0700, Samuel Sieb wrote:
> As Jonathan mentioned in a previous reply, systemd is using symlinks for
> temporary data storage, like a dictionary or map depending on which
> programming language you're using.
Kinda wierd. I wonder what the advantage is over creating
On 9/18/22 16:44, Stephen Morris wrote:
Just an FYI, I've issued ll /run/systemd/units and on my system
that folder contains nothing but symlinks and everyone of them are
pointing at files that don't exist. If these are created every boot,
then what is FC36 doing wrong to create invalid
On 17/9/22 01:48, stan via users wrote:
On Fri, 16 Sep 2022 14:55:11 +1000
"Michael D. Setzer II via users" wrote:
I've run this little script from time to time in /
find . -xtype l >/badlinks 2>ERR
grep -v '/proc\|/run' /badlinks-clean
At present ends up with other 300 lines in the
On Sep 16, 2022, at 20:44, Michael D. Setzer II via users
wrote:
>
> Was not aware of that program? Was already installed on my system. Following
> instructions from link, it found 279 of the broken links under /usr and after
> checking, I went ahead are removed them.
> Doing the run using /
On Sat, 17 Sep 2022 10:43:45 +1000
"Michael D. Setzer II via users" wrote:
> Then there are some listed as messy: and other_fs:??
>
> cut -f1 -d:35611 absolute
> 29 dangling
> 236 messy
> 56 other_fs
>
> Learn new things all the time. Thanks.
Ditto. I wasn't aware of the
vice
dangling: /etc/systemd/system/sysinit.target.wants/fedora-import-state.service
->
/usr/lib/systemd/system/fedora-import-state.service
dangling: /etc/systemd/system/sysinit.target.wants/lvm2-lvmetad.socket ->
/usr/lib/systemd/system/lvm2-lvmetad.socket
dangling:
xrwx. 1 root root 15 Sep 17 06:19 test1 ->
> /badlinks-clean
> lrwxrwxrwx. 1 root root 16 Sep 17 06:19 test2 ->
> /badlinks-cleanx
>
> Both badlinks and badlinks-clean only contain
> ./test2
>
> So only seems to list links that are broken.
>
>
> On 16 Sep 2022 at 18
oot 16 Sep 17 06:19 test2 ->
/badlinks-cleanx
Both badlinks and badlinks-clean only contain
./test2
So only seems to list links that are broken.
On 16 Sep 2022 at 18:50, Patrick O'Callaghan wrote:
Subject: Re: Question on bad links?
From: Patrick O'Cal
On Sat, 2022-09-17 at 02:58 +1000, Michael D. Setzer II via users
wrote:
> Not clear on differnce be -l and -L?
They have completely different meanings:
'-xtype l' finds files which are themselves symlinks. That's what your
script is doing. Nothing I can see in the script detects that those
On 16 Sep 2022 at 8:48, stan wrote:
Date sent: Fri, 16 Sep 2022 08:48:29 -0700
From: stan
To: users@lists.fedoraproject.org
Copies to: mi...@guam.net
Subject:Re: Question on bad links?
Organization
On Fri, 16 Sep 2022 14:55:11 +1000
"Michael D. Setzer II via users" wrote:
> I've run this little script from time to time in /
>
> find . -xtype l >/badlinks 2>ERR
> grep -v '/proc\|/run' /badlinks-clean
>
> At present ends up with other 300 lines in the
> badlinks-clean
>
> Cleaned up a
On Fri, 2022-09-16 at 14:55 +1000, Michael D. Setzer II via users
wrote:
> I've run this little script from time to time in /
>
> find . -xtype l >/badlinks 2>ERR
> grep -v '/proc\|/run' /badlinks-clean
Not really relevant to your question, but you could make this a one-
liner:
find / -xtype l
I've run this little script from time to time in /
find . -xtype l >/badlinks 2>ERR
grep -v '/proc\|/run' /badlinks-clean
At present ends up with other 300 lines in the
badlinks-clean
Cleaned up a number of bad lines in a jre directory that
seemed to be left over stuff from fc27 to fc33?
27 matches
Mail list logo
