[SOLVED] Bash, maximum file/folder listing, ls -a? Why no /run/5000/?

maybeJosiah · 01-20-2024, 12:18 PM

Anyway, maybe it is only when I run like my program. Good to know things in there are temporary. I guess I do not need this then. X E.

maybeJosiah · 01-20-2024, 12:21 PM

Screenshot. X E.

TB0ne · 01-20-2024, 12:26 PM

Quote:

Originally Posted by maybeJosiah

@Tb0ne, #4 should state the problem in its entirety that I am trying to solve. X E.

Wrong; it states one step in what you're trying to do, and you got a very clear explanation of what it is and why it doesn't matter in post #3. Did you not read/understand it??

AGAIN: What is the *ROOT PROBLEM* you're trying to 'solve'??? Seems to all center around backing things up, and you're just not paying attention/understanding what you're told.

Petri Kaukasoina · 01-20-2024, 12:27 PM

I don't have Ubuntu, so the directory structure can be different. My UID is 5591.

Code:

$ TZ=UTC ls -al /run/user/5591 
total 0
drwx------ 8 kaukasoi users 160 2024-01-18 15:31 .
drwxr-xr-x 3 root     root   60 2024-01-18 15:28 ..
drwx------ 3 kaukasoi users  60 2024-01-18 15:28 dbus-1
drwx------ 2 kaukasoi users  60 2024-01-18 15:31 dconf
dr-x------ 2 kaukasoi users   0 1970-01-01 00:00 doc
dr-x------ 2 kaukasoi users   0 2024-01-18 15:31 gvfs
drwx------ 2 kaukasoi users  40 2024-01-18 15:31 gvfsd
drwx------ 2 kaukasoi users  80 2024-01-18 15:31 pulse

As root:

Code:

# TZ=UTC ls -al /run/user/5591 
ls: cannot access '/run/user/5591/gvfs': Permission denied
ls: cannot access '/run/user/5591/doc': Permission denied
total 0
drwx------ 8 kaukasoi users 160 2024-01-18 15:31 .
drwxr-xr-x 3 root     root   60 2024-01-18 15:28 ..
drwx------ 3 kaukasoi users  60 2024-01-18 15:28 dbus-1
drwx------ 2 kaukasoi users  60 2024-01-18 15:31 dconf
d????????? ? ?        ?       ?                ? doc
d????????? ? ?        ?       ?                ? gvfs
drwx------ 2 kaukasoi users  40 2024-01-18 15:31 gvfsd
drwx------ 2 kaukasoi users  80 2024-01-18 15:31 pulse

'mount' tells that doc and gvfs are fuse file systems, mounted on /run/user/5591 which is tmpfs, mounted on /run which also is tmpfs.

Code:

$ mount |grep run
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=32768k,mode=755,inode64)
tmpfs on /run/user/5591 type tmpfs (rw,nosuid,nodev,relatime,size=594636k,nr_inodes=148659,mode=700,uid=5591,gid=100,inode64)
gvfsd-fuse on /run/user/5591/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=5591,group_id=100)
portal on /run/user/5591/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=5591,group_id=100)

To allow root see inside fuse mounts, 'allow_root' mount option would be needed when the fuse mounts are made.

None of these are on the disk drive. You should use 'find -xdev' to not descend to other file system mounts.

michaelk · 01-20-2024, 12:29 PM

You do not need anything in /run.

I would actually guess the directory in question is /run/user/1000. With 1000 being the first UID for a regular user. The permissions of that directory should be something like:

Quote:

drwx------ 14 user_name user_name 480 Jan 20 09:41 /run/user/1000

For ls to list the contents you need x permissions but since root does not have access i.e. no permission for others your script fails.

maybeJosiah · 01-20-2024, 01:25 PM

I consider this solved by not needing to record /run and that /run is temporary stuff so "find" may have just been creating something. X E.

maybeJosiah · 01-20-2024, 03:00 PM

P.S. I did see /run/user/1000 in like my new recording. I am certain it was /run/5000 with "find". Probably a temporary thing for "find". X E.