[SOLVED] Wrong user/group of subdir and file created in /home/usernamedir/tmp

mackowiakp · 11-10-2020, 11:08 AM

I have Debian Buster installed in LXC container on QNAP NAS. From container I run such script:

Code:

debian@Debian:~/Pobrane$ cat ampli 
#!/bin/bash

path_media="/share/homes/media/Pobrane/RADIO"
ssh_cmd="/usr/bin/ssh -p669 -x -q -i /home/debian/.ssh/id_debian admin@192.168.0.7"

[ ! -d /home/debian/tmp ] && mkdir /home/debian/tmp
$ssh_cmd $path_media/ampli $1 > /home/debian/tmp/ampli

Script "ampli" returns text output to stdout. The content of output is ok.
But both "/home/debian/tmp" dir and "/home/debian/tmp/ampli" file have user/group - root/root. Should be debian/debian. Why is not? Any idea?

sgosnell · 11-10-2020, 02:03 PM

Are you running ampli as root?

mackowiakp · 11-10-2020, 02:07 PM

Of course NOT. I running it as user "debian". It is very strange for me. The same situation is when I try to create such file in /dev/shm/ (more useful for me). Can not access the file created by the script because once has root/root uid/gid.

sgosnell · 11-10-2020, 02:55 PM

/dev/shm/ and everything in it does belong to root. I don't understand why that is more useful, but you don't want to change the owner & group of anything in /dev. I ran your script (modified) from my home, and while it didn't entirely work because of not having packages installed, it did create the directories in my home, and they are owned by me. If you're running the script from outside your home, that may be why the directories are owned by root. Try running it as your user, from your home directory, and see what you get.

mackowiakp · 11-11-2020, 01:29 AM

The case was cleared up. Never in my life would I have guessed the reason.
Well, due to a problem with QNAP CloudSync app, I had an open online support session with QNAP Support. As I learned from the QNAP Helpdesk, such a session causes each console session (no matter how initialized) to run it with root privileges.
And it doesn't matter that the system shows that I am a normal user and not root. Only that I do not work on the "native" QNAP partition, but in the LXC container. But according to the QNAP Helpdesk, it doesn't matter.
I don't understand it at all. Nevertheless, after disconnecting the support session, the script works fine. Complete quirk ...