On Sun, Aug 27, 2023 at 02:17:06PM -0400, Jeffrey Walton wrote:
[...]
> The symlink tool works great, too:
>
> symlink -r / | grep dangling
>
> You can also delete them, once you verify they are dangling:
>
> symlink -r -d /
>
> In fact, it is a recommended post-upgrade step for
On Sun, Aug 27, 2023 at 1:10 PM Jörg-Volker Peetz wrote:
>
> to...@tuxteam.de wrote on 24/08/2023 14:00:
> >
> > A couple of days ago I was searching for dangling symlinks.
> >
> >find . -follow -lname "*"
> >
> How about
> find -L . -type l
The symlink tool works great, too:
On Sun, Aug 27, 2023 at 07:09:36PM +0200, Jörg-Volker Peetz wrote:
> to...@tuxteam.de wrote on 24/08/2023 14:00:
> >
> > A couple of days ago I was searching for dangling symlinks.
> >
> >find . -follow -lname "*"
> >
> How about
>find -L . -type l
Should work, too.
Cheers
--
t
to...@tuxteam.de wrote on 24/08/2023 14:00:
A couple of days ago I was searching for dangling symlinks.
find . -follow -lname "*"
How about
find -L . -type l
Regards,
Jörg.
> > to...@tuxteam.de (12023-08-24):
> > > Dunno. I use find nearly every day. Seeing it as "just a recursive
> > > grep" doesn't cover a fraction of its usefulness.
> > >
> > > A couple of days ago I was searching for dangling symlinks.
> > >
> > > find . -follow -lname "*"
Wow... what a
Stanislav Vlasov (12023-08-24):
> Sometimes it's unexpected :-)
Then the shell prints an error and I try again. Still less time wasted
than these two mails.
Regards,
--
Nicolas George
чт, 24 авг. 2023 г. в 18:17, Nicolas George :
> > With a really large amount of files there will be overflow of process
> > environment (or too large cmdline).
> If I expect a very large amount of files, I can use it another way.
Sometimes it's unexpected :-)
--
Stanislav
On Thu, Aug 24, 2023 at 02:05:48PM +0200, Nicolas George wrote:
> to...@tuxteam.de (12023-08-24):
> > Dunno. I use find nearly every day. Seeing it as "just a recursive
> > grep" doesn't cover a fraction of its usefulness.
> >
> > A couple of days ago I was searching for dangling symlinks.
> >
>
Stanislav Vlasov (12023-08-24):
> With a really large amount of files there will be overflow of process
> environment (or too large cmdline).
If I expect a very large amount of files, I can use it another way.
--
Nicolas George
чт, 24 авг. 2023 г. в 17:06, Nicolas George :
>
> to...@tuxteam.de (12023-08-24):
> > Dunno. I use find nearly every day. Seeing it as "just a recursive
> > grep" doesn't cover a fraction of its usefulness.
> >
> > A couple of days ago I was searching for dangling symlinks.
> >
> > find .
to...@tuxteam.de (12023-08-24):
> Dunno. I use find nearly every day. Seeing it as "just a recursive
> grep" doesn't cover a fraction of its usefulness.
>
> A couple of days ago I was searching for dangling symlinks.
>
> find . -follow -lname "*"
ls **/*(N@-@)
Zsh rulz.
Regards,
--
On Thu, Aug 24, 2023 at 01:52:28PM +0200, Oliver Schoede wrote:
[...]
> Have basically stopped using traditional 'find' outside of scripts, as
> always thought I was about the last one [...]
Dunno. I use find nearly every day. Seeing it as "just a recursive
grep" doesn't cover a fraction of its
ug
>> > 21 13:29 .mozilla/firefox/gs0gkgv2.default/favicons.sqlite 1515049
>> > 260 -rw-r--r-- 1 myusername myusername 262144 Aug 18 22:36
>> > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite
>>
>> For me command "locate" is easier t
On Mon, Aug 21, 2023 at 06:45:16PM +0100, Brian wrote:
[...]
> plocate-updatedb.service and plocate-updatedb.timer take care of
> that for me. :)
I admit to accepting some help from trusty cron :)
> > Tools, jobs and that :)
>
> Indeed.
Cheers
--
t
signature.asc
Description: PGP signature
On 2023-08-21 17:21, to...@tuxteam.de wrote:
On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote:
On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de:
>> For me command "locate" is easier to use than "find":
>
> They do different things. Locate i
On Mon, Aug 21, 2023 at 02:50:07PM +, Michael Kjörling wrote:
> On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de:
> >> For me command "locate" is easier to use than "find":
> >
> > They do different things. Locate is much faster, but it only l
On 21 Aug 2023 15:56 +0200, from to...@tuxteam.de:
>> For me command "locate" is easier to use than "find":
>
> They do different things. Locate is much faster, but it only looks
> into file names. Find can do nearly everything, like looking into
> file met
lite
> > 1515049 260 -rw-r--r-- 1 myusername myusername 262144 Aug 18 22:36
> > .mozilla/firefox/th3dv2jy.default-1461749950404/favicons.sqlite
>
> For me command "locate" is easier to use than "find":
They do different things. Locate is much faster, bu
/th3dv2jy.default-1461749950404/favicons.sqlite
For me command "locate" is easier to use than "find":
rprice@titan ~ locate favicons.sqlite
/mnt/home/rprice/.mozilla/firefox/60mahk24.default-esr/favicons.sqlite
/mnt/home/rprice/.mozilla/firefox/60mahk24.default-esr/favicons.
19 matches
Mail list logo
