Message-ID:

The devil can cite Scripture for his purpose. -- William Shakespeare, "The Merchant of Venice"

comp / comp.unix.questions / Re: find prune >

Subject: find prune >
From: Bit Twister
Newsgroups: comp.unix.questions
Organization: A noiseless patient Spider
Date: Tue, 25 Jul 2023 13:44 UTC

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: BitTwister@mouse-potato.com (Bit Twister)
Newsgroups: comp.unix.questions
Subject: find prune >
Date: Tue, 25 Jul 2023 08:44:58 -0500
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <slrnubvket.1qkju.BitTwister@wb.home.arpa>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Info: dont-email.me; posting-host="b0c7c41af789bd174b93204514ec94da";
logging-data="1198993"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/JJxGKLsm8qMYPG3RwsLpLoJjHSqNuPUM="
User-Agent: slrn/pre1.0.4-6 (Linux)
Cancel-Lock: sha1:0sFEqpre403aQVwQ10e/YCzooYI=

View all headers

I am getting numerous find errors: Example /userX is just example only
real account names are being used on system.

# find / $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
-prune -o -user normal -o -group normal

find: ‘/user1/.gvfs’: Permission denied
find: ‘/user2/.gvfs’: Permission denied
find: ‘/user3/.gvfs’: Permission denied
find: ‘/run/user4/1800/doc’: Permission denied
find: ‘/run/user5/1800/gvfs’: Permission denied
find: ‘/user6/.gvfs’: Permission denied
find: ‘/user7/.gvfs’: Permission denied
find: ‘/user8/.gvfs’: Permission denied
find: ‘/run/user9/1800/doc’: Permission denied
find: ‘/run/user10/1800/gvfs’: Permission denied

I would like to prune the /.gvfs and /run/ Permission denied problems.
Any suggestions welcome and thanks in advance.

Current command being used, as root in a custom system audit bash script:

find / $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
-prune -o -user user12 -o -group user12

Subject: Re: find prune >
From: Helmut Waitzmann
Newsgroups: comp.unix.questions
Organization: A noiseless patient Spider
Date: Sun, 30 Jul 2023 19:14 UTC
References: 1

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nn.throttle@xoxy.net (Helmut Waitzmann)
Newsgroups: comp.unix.questions
Subject: Re: find prune >
Date: Sun, 30 Jul 2023 21:14:39 +0200
Organization: A noiseless patient Spider
Lines: 36
Sender: Helmut Waitzmann <12f7e638@mail.de>
Message-ID: <83jzuh6wkg.fsf@helmutwaitzmann.news.arcor.de>
References: <slrnubvket.1qkju.BitTwister@wb.home.arpa>
Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c <oe.throttle@xoxy.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Info: dont-email.me; posting-host="cf8c369450eb659b9642bc02915f132e";
logging-data="3165559"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Pk1C7KbTfFZAKqzqslg6Z1jzOLxwxf38="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
Cancel-Lock: sha1:cd8hIN8fqQ978rGPJgjhs0r8ep8=
sha1:Pt3+zTk+e4AYhFTboAs62ev21vc=
Mail-Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c <oe.throttle@xoxy.net>
Mail-Copies-To: nobody

View all headers

Bit Twister <BitTwister@mouse-potato.com>:
> I am getting numerous find errors: Example /userX is just
> example only real account names are being used on system.
>
>
> # find / $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
> -prune -o -user normal -o -group normal
>
> find: ‘/user1/.gvfs’: Permission denied
> find: ‘/user2/.gvfs’: Permission denied
> find: ‘/user3/.gvfs’: Permission denied
> find: ‘/run/user4/1800/doc’: Permission denied
> find: ‘/run/user5/1800/gvfs’: Permission denied
> find: ‘/user6/.gvfs’: Permission denied
> find: ‘/user7/.gvfs’: Permission denied
> find: ‘/user8/.gvfs’: Permission denied
> find: ‘/run/user9/1800/doc’: Permission denied
> find: ‘/run/user10/1800/gvfs’: Permission denied
>
> I would like to prune the /.gvfs and /run/ Permission denied
> problems. Any suggestions welcome and thanks in advance.
>

Please describe (i. e. specify) (in plain english words) the
exact criterion to distinguish whether a file or directory should
be found resp. ignored and whether a directory should be
descended into resp. pruned. Consider specifying e. g. the names
and the paths of the pathnames "find" should care of as well as their
ownerships and group memberships and the access rights they should
grant.

Only then will you (or somebody else) be able to set up an
appropriate "find" command.

Subject: Re: find prune >
From: Bit Twister
Newsgroups: comp.unix.questions
Organization: A noiseless patient Spider
Date: Mon, 31 Jul 2023 01:36 UTC
References: 1 2

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: BitTwister@mouse-potato.com (Bit Twister)
Newsgroups: comp.unix.questions
Subject: Re: find prune >
Date: Sun, 30 Jul 2023 20:36:57 -0500
Organization: A noiseless patient Spider
Lines: 43
Message-ID: <slrnuce41p.aac4.BitTwister@wb.home.arpa>
References: <slrnubvket.1qkju.BitTwister@wb.home.arpa>
<83jzuh6wkg.fsf@helmutwaitzmann.news.arcor.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Info: dont-email.me; posting-host="daef28dddb0912126afe0d85c3b3baa5";
logging-data="3339628"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX181JxJcYo8jukly6AYnBHcAzC3VWMOjGGs="
User-Agent: slrn/pre1.0.4-6 (Linux)
Cancel-Lock: sha1:Wa5YGTeugBu4M0tBGMm97w9Au4o=

View all headers

On Sun, 30 Jul 2023 21:14:39 +0200, Helmut Waitzmann wrote:
> Bit Twister <BitTwister@mouse-potato.com>:
>> I am getting numerous find errors: Example /userX is just
>> example only real account names are being used on system.
>>
>>
>> # find / $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
>> -prune -o -user normal -o -group normal
>>
>> find: ‘/user1/.gvfs’: Permission denied
>> find: ‘/user2/.gvfs’: Permission denied
>> find: ‘/user3/.gvfs’: Permission denied
>> find: ‘/run/user4/1800/doc’: Permission denied
>> find: ‘/run/user5/1800/gvfs’: Permission denied
>> find: ‘/user6/.gvfs’: Permission denied
>> find: ‘/user7/.gvfs’: Permission denied
>> find: ‘/user8/.gvfs’: Permission denied
>> find: ‘/run/user9/1800/doc’: Permission denied
>> find: ‘/run/user10/1800/gvfs’: Permission denied
>>
>> I would like to prune the /.gvfs and /run/ Permission denied
>> problems. Any suggestions welcome and thanks in advance.
>>
>
> Please describe (i. e. specify) (in plain english words) the
> exact criterion to distinguish whether a file or directory should
> be found resp. ignored and whether a directory should be
> descended into resp. pruned. Consider specifying e. g. the names
> and the paths of the pathnames "find" should care of as well as their
> ownerships and group memberships and the access rights they should
> grant.
>
>
> Only then will you (or somebody else) be able to set up an
> appropriate "find" command.

Hmm, anyone who can show the appropriate "find" command can see
most of your "Please describe" requirements. The error messages
are what I want ignored, not showed/reported.

Subject: Re: find prune >
From: Helmut Waitzmann
Newsgroups: comp.unix.questions
Organization: A noiseless patient Spider
Date: Mon, 31 Jul 2023 03:30 UTC
References: 1 2 3

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nn.throttle@xoxy.net (Helmut Waitzmann)
Newsgroups: comp.unix.questions
Subject: Re: find prune >
Date: Mon, 31 Jul 2023 05:30:47 +0200
Organization: A noiseless patient Spider
Lines: 64
Sender: Helmut Waitzmann <12f7e638@mail.de>
Message-ID: <83edko7o60.fsf@helmutwaitzmann.news.arcor.de>
References: <slrnubvket.1qkju.BitTwister@wb.home.arpa>
<83jzuh6wkg.fsf@helmutwaitzmann.news.arcor.de>
<slrnuce41p.aac4.BitTwister@wb.home.arpa>
Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c <oe.throttle@xoxy.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Info: dont-email.me; posting-host="f78dbd6cbc9ebbcbc0e07b678c2380e0";
logging-data="3356989"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19j/w125nieCnvSnvXx56zpo9WDThoOHKs="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
Cancel-Lock: sha1:fx+7xQ4y/1XSDKkGTT0pgHb1MXY=
sha1:kplAAyKmPkJLqnQCRwvzW8IO2sk=
Mail-Copies-To: nobody
Mail-Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c <oe.throttle@xoxy.net>

View all headers

Bit Twister <BitTwister@mouse-potato.com>:
> On Sun, 30 Jul 2023 21:14:39 +0200, Helmut Waitzmann wrote:
>> Bit Twister <BitTwister@mouse-potato.com>:
>>> I am getting numerous find errors: Example /userX is just
>>> example only real account names are being used on system.
>>>
>>>
>>> # find / $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
>>> -prune -o -user normal -o -group normal
>>>
>>> find: ‘/user1/.gvfs’: Permission denied
>>> find: ‘/user2/.gvfs’: Permission denied
>>> find: ‘/user3/.gvfs’: Permission denied
>>> find: ‘/run/user4/1800/doc’: Permission denied
>>> find: ‘/run/user5/1800/gvfs’: Permission denied
>>> find: ‘/user6/.gvfs’: Permission denied
>>> find: ‘/user7/.gvfs’: Permission denied
>>> find: ‘/user8/.gvfs’: Permission denied
>>> find: ‘/run/user9/1800/doc’: Permission denied
>>> find: ‘/run/user10/1800/gvfs’: Permission denied
>>>
>>> I would like to prune the /.gvfs and /run/ Permission denied
>>> problems. Any suggestions welcome and thanks in advance.
>>>
>>
>> Please describe (i. e. specify) (in plain english words) the
>> exact criterion to distinguish whether a file or directory should
>> be found resp. ignored and whether a directory should be
>> descended into resp. pruned. Consider specifying e. g. the names
>> and the paths of the pathnames "find" should care of as well as their
>> ownerships and group memberships and the access rights they should
>> grant.
>>
>>
>> Only then will you (or somebody else) be able to set up an
>> appropriate "find" command.
>>
>
> Hmm, anyone who can show the appropriate "find" command can see
> most of your "Please describe" requirements. The error messages
> are what I want ignored, not showed/reported.
>

If all you want to do is to avoid "find" to run into a lack of
permissions, you could do

find / \
-type d ! $ -exec test -x \{\} \; -exec test -r \{\} \; $ \
! -prune \
-o \
$ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
-prune -o -user normal -o -group normal

That will prevent "find" from trying to descend into any
directory that lacks the search or read permission.

But that will of course hide even errorneously lacking read and
execute permissions on any directory.

Subject: Re: find prune >
From: Bit Twister
Newsgroups: comp.unix.questions
Organization: A noiseless patient Spider
Date: Mon, 31 Jul 2023 03:56 UTC
References: 1 2 3 4

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: BitTwister@mouse-potato.com (Bit Twister)
Newsgroups: comp.unix.questions
Subject: Re: find prune >
Date: Sun, 30 Jul 2023 22:56:19 -0500
Organization: A noiseless patient Spider
Lines: 77
Message-ID: <slrnucec73.ancn.BitTwister@wb.home.arpa>
References: <slrnubvket.1qkju.BitTwister@wb.home.arpa>
<83jzuh6wkg.fsf@helmutwaitzmann.news.arcor.de>
<slrnuce41p.aac4.BitTwister@wb.home.arpa>
<83edko7o60.fsf@helmutwaitzmann.news.arcor.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Info: dont-email.me; posting-host="daef28dddb0912126afe0d85c3b3baa5";
logging-data="3358250"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19OIlGeMkKv/notliFn5+72zzcm4R4O+Ow="
User-Agent: slrn/pre1.0.4-6 (Linux)
Cancel-Lock: sha1:0bOdclfdMaGGQMLByKctH9MX2dw=

View all headers

On Mon, 31 Jul 2023 05:30:47 +0200, Helmut Waitzmann wrote:
> Bit Twister <BitTwister@mouse-potato.com>:
>> On Sun, 30 Jul 2023 21:14:39 +0200, Helmut Waitzmann wrote:
>>> Bit Twister <BitTwister@mouse-potato.com>:
>>>> I am getting numerous find errors: Example /userX is just
>>>> example only real account names are being used on system.
>>>>
>>>>
>>>> # find / $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
>>>> -prune -o -user normal -o -group normal
>>>>
>>>> find: ‘/user1/.gvfs’: Permission denied
>>>> find: ‘/user2/.gvfs’: Permission denied
>>>> find: ‘/user3/.gvfs’: Permission denied
>>>> find: ‘/run/user4/1800/doc’: Permission denied
>>>> find: ‘/run/user5/1800/gvfs’: Permission denied
>>>> find: ‘/user6/.gvfs’: Permission denied
>>>> find: ‘/user7/.gvfs’: Permission denied
>>>> find: ‘/user8/.gvfs’: Permission denied
>>>> find: ‘/run/user9/1800/doc’: Permission denied
>>>> find: ‘/run/user10/1800/gvfs’: Permission denied
>>>>
>>>> I would like to prune the /.gvfs and /run/ Permission denied
>>>> problems. Any suggestions welcome and thanks in advance.
>>>>
>>>
>>> Please describe (i. e. specify) (in plain english words) the
>>> exact criterion to distinguish whether a file or directory should
>>> be found resp. ignored and whether a directory should be
>>> descended into resp. pruned. Consider specifying e. g. the names
>>> and the paths of the pathnames "find" should care of as well as their
>>> ownerships and group memberships and the access rights they should
>>> grant.
>>>
>>>
>>> Only then will you (or somebody else) be able to set up an
>>> appropriate "find" command.
>>>
>>
>> Hmm, anyone who can show the appropriate "find" command can see
>> most of your "Please describe" requirements. The error messages
>> are what I want ignored, not showed/reported.
>>
>
> If all you want to do is to avoid "find" to run into a lack of
> permissions, you could do
>
>
> find / \
> -type d ! $ -exec test -x \{\} \; -exec test -r \{\} \; $ \
> ! -prune \
> -o \
> $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
> -prune -o -user normal -o -group normal
>
>
> That will prevent "find" from trying to descend into any
> directory that lacks the search or read permission.
>
>
> But that will of course hide even errorneously lacking read and
> execute permissions on any directory.
>

No joy here, Still getting Permission denied. :(

# find / \
> -type d ! $ -exec test -x \{\} \; -exec test -r \{\} \; $ \
> ! -prune \
> -o \
> $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
> -prune -o -user normal -o -group normal
find: ‘/accounts/user_1/.cache/gvfs’: Permission denied
find: ‘/accounts/user_1/.cache/doc’: Permission denied
find: ‘/run/user/1800/doc’: Permission denied
find: ‘/run/user/1800/gvfs’: Permission denied

Subject: Re: find prune >
From: Helmut Waitzmann
Newsgroups: comp.unix.questions
Organization: A noiseless patient Spider
Date: Wed, 2 Aug 2023 18:00 UTC
References: 1 2 3 4 5

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: nn.throttle@xoxy.net (Helmut Waitzmann)
Newsgroups: comp.unix.questions
Subject: Re: find prune >
Date: Wed, 02 Aug 2023 20:00:22 +0200
Organization: A noiseless patient Spider
Lines: 20
Sender: Helmut Waitzmann <12f7e638@mail.de>
Message-ID: <835y5x72a1.fsf@helmutwaitzmann.news.arcor.de>
References: <slrnubvket.1qkju.BitTwister@wb.home.arpa>
<83jzuh6wkg.fsf@helmutwaitzmann.news.arcor.de>
<slrnuce41p.aac4.BitTwister@wb.home.arpa>
<83edko7o60.fsf@helmutwaitzmann.news.arcor.de>
<slrnucec73.ancn.BitTwister@wb.home.arpa>
Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c <oe.throttle@xoxy.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Info: dont-email.me; posting-host="4d8775ebfb7cb3a0f1ccdb5a9e99fbb1";
logging-data="234817"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18k1CDAmWfdGus+E/uYuJg9xe83F6SQMec="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
Cancel-Lock: sha1:qjBz30GPZrAFmuXqMffOKA8jE1M=
sha1:lTxuJ/VpE6OsJ6gfudrXI3QputI=
Mail-Reply-To: Helmut Waitzmann Anti-Spam-Ticket.b.qc3c <oe.throttle@xoxy.net>
Mail-Copies-To: nobody

View all headers

Bit Twister <BitTwister@mouse-potato.com>:
> On Mon, 31 Jul 2023 05:30:47 +0200, Helmut Waitzmann wrote:
> No joy here, Still getting Permission denied. :(
>
>
> # find / \
>> -type d ! $ -exec test -x \{\} \; -exec test -r \{\} \; $ \
>> ! -prune \
>> -o \
>> $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
>> -prune -o -user normal -o -group normal
> find: ‘/accounts/user_1/.cache/gvfs’: Permission denied
> find: ‘/accounts/user_1/.cache/doc’: Permission denied
> find: ‘/run/user/1800/doc’: Permission denied
> find: ‘/run/user/1800/gvfs’: Permission denied

I can't see how that "find" command could produce those error
messages. Could you show more context of the "find" invocation?

Subject: Re: find prune >
From: Bit Twister
Newsgroups: comp.unix.questions
Organization: A noiseless patient Spider
Date: Wed, 2 Aug 2023 23:05 UTC
References: 1 2 3 4 5 6

Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: user_1@mouse-potato.com (Bit Twister)
Newsgroups: comp.unix.questions
Subject: Re: find prune >
Date: Wed, 2 Aug 2023 18:05:06 -0500
Organization: A noiseless patient Spider
Lines: 54
Message-ID: <slrnuclo97.va28.BitTwister@wb.home.arpa>
References: <slrnubvket.1qkju.user_1@wb.home.arpa>
<83jzuh6wkg.fsf@helmutwaitzmann.news.arcor.de>
<slrnuce41p.aac4.user_1@wb.home.arpa>
<83edko7o60.fsf@helmutwaitzmann.news.arcor.de>
<slrnucec73.ancn.user_1@wb.home.arpa>
<835y5x72a1.fsf@helmutwaitzmann.news.arcor.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Info: dont-email.me; posting-host="78850cb57d4517685ee2d93f0e17ae51";
logging-data="344012"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/xAPaEHnM6Jk7igYa1xJdAvRIP1llyHFo="
User-Agent: slrn/pre1.0.4-6 (Linux)
Cancel-Lock: sha1:DP0q0FKmwbKPchIpc/Wdt8uy5PI=

View all headers

On Wed, 02 Aug 2023 20:00:22 +0200, Helmut Waitzmann wrote:
> Bit Twister <user_1@mouse-potato.com>:
>> On Mon, 31 Jul 2023 05:30:47 +0200, Helmut Waitzmann wrote:
>> No joy here, Still getting Permission denied. :(
>>
>>
>> # find / \
>>> -type d ! $ -exec test -x \{\} \; -exec test -r \{\} \; $ \
>>> ! -prune \
>>> -o \
>>> $ -path /home -o -path /proc -o -path /var/lib/named/proc $ \
>>> -prune -o -user normal -o -group normal
>> find: ‘/accounts/user_1/.cache/gvfs’: Permission denied
>> find: ‘/accounts/user_1/.cache/doc’: Permission denied
>> find: ‘/run/user/1800/doc’: Permission denied
>> find: ‘/run/user/1800/gvfs’: Permission denied
>
>
> I can't see how that "find" command could produce those error
> messages. Could you show more context of the "find" invocation?

I do not understand more context, The above output was a cut/past of the
find command and results except for me changing real user names
to user_x values.

$ ls -al /run/user/1800/

total 4.0K
drwx------ 2 user_1 user_1 60 Jul 31 00:45 at-spi
srw-rw-rw- 1 user_1 user_1 0 Jul 31 00:45 bus
drwx------ 2 user_1 user_1 60 Jul 31 06:57 claws-mail
drwx------ 3 user_1 user_1 60 Jul 31 00:45 dbus-1
drwx------ 2 user_1 user_1 40 Aug 2 04:17 dconf
dr-x------ 2 user_1 user_1 0 Dec 31 1969 doc
drwx------ 2 user_1 user_1 40 Aug 2 11:30 geany
drwx------ 2 user_1 user_1 120 Jul 31 06:56 gnupg
dr-x------ 2 user_1 user_1 0 Jul 31 00:45 gvfs
drwx------ 2 user_1 user_1 40 Jul 31 00:45 gvfsd
-rw------- 1 user_1 user_1 350 Jul 31 06:56 ICEauthority
drwx------ 2 user_1 user_1 80 Jul 31 06:56 pulse
drwxr-xr-x 5 user_1 user_1 140 Jul 31 00:45 systemd

$ mount | grep 1800
tmpfs on /run/user/1800 type tmpfs (rw,nosuid,nodev,relatime,size=1550052k,nr_inodes=387513,mode=700,uid=1800,gid=1800,inode64)
gvfsd-fuse on /run/user/1800/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1800,group_id=1800)
portal on /run/user/1800/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1800,group_id=1800)

As root I get this snippet
# ls -al /run/user/1800/
drwx------ 2 user_1 user_1 40 Aug 2 04:17 dconf
d????????? ? ? ? ? ? doc
drwx------ 2 user_1 user_1 60 Aug 2 17:57 geany
drwx------ 2 user_1 user_1 120 Jul 31 06:56 gnupg
d????????? ? ? ? ? ? gvfs

Subject	Author
find prune >	Bit Twister
Re: find prune >	Helmut Waitzmann
Re: find prune >	Bit Twister
Re: find prune >	Helmut Waitzmann
Re: find prune >	Bit Twister
Re: find prune >	Helmut Waitzmann
Re: find prune >	Bit Twister