Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have problem with Ubuntu.
I'm trying add user tbalicek to group www-data but the following commands doesn't work.
tbalicek#UBK-LINUX:/var/www$ sudo usermod -a -G www-data tbalicek
tbalicek#UBK-LINUX:/var/www$ groups
tbalicek sudo
tbalicek#UBK-LINUX:/var/www$ groups tbalicek
tbalicek : tbalicek www-data
I don't understand why groups and groups tbalicek return different results?? When I'm loged like tbalicek
When I'm trying mkdir like tbalicek in folder where si own group www-data I get: permission denied
tbalicek#UBK-LINUX:/var/www$ ls -ltr
total 20
-rwxrwxr-x 1 www-data www-data 31 Mar 27 13:52 index.php
drwxrwxr-x 9 www-data www-data 4096 Mar 27 17:16 pelnar
drwxrwxr-x 16 www-data www-data 4096 Mar 27 17:21 redmine
drwxrwxr-x 9 www-data www-data 4096 Apr 3 17:54 taskagent
-rwxrwxr-x 1 root root 22 Apr 10 14:35 info.php
tbalicek#UBK-LINUX:/var/www$
Group assignments don't take effect in the current shell. You have to log out and log back in to see the group changes.
From the Debian Wiki for sudo:
After being added to a new group the user must log out and then log back in again for the new group to take effect. Groups are only assigned to users at login time. A most common source of confusion is that people add themselves to a new group but then do not log out and back in again and then have problems because the group is not assigned.
You might get a better response for this sort of question on ServerFault.
Try the newgrp command:
ts#cmp:~$ id
uid=1001(ts) gid=1001(ts) groups=1001(ts),27(sudo)
ts#cmp:~$ newgrp www-data
ts#cmp:~$ id
uid=1001(ts) gid=33(www-data) groups=1001(ts),27(sudo),33(www-data)
Just a nitpick, 'sudo adduser user group' will also add a user to a group and I find the syntax easier to remember than using usermod.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Ubuntu 20 LTS, Installed laradock,
in Ubuntu
$ pwd
/root/Docker
$ ls
blog laradock
$ rsync -a /media/sf_code/blog . && chmod -R 755 blog
$ cd laracock
$ docker-compose exec --user=root workspace bash
in docker
> ll
total 20
drwxr-xr-x 4 laradock laradock 4096 Nov 12 06:52 ./
drwxr-xr-x 1 root root 4096 Nov 12 02:30 ../
drwxr-xr-x 12 root 998 4096 Nov 12 03:09 blog/
drwxr-xr-x 74 laradock laradock 4096 Nov 12 06:35 laradock/
what does 998 mean?
The 4th column is the group id. It there is an entry in /etc/group with this id, then the group name will be printed otherwise the id.
The your example the group id of folder blog is 998 but no group exist inside the container with this id. Mapping a folder to a docker container does not change owner or group.
Some explanation can be found here
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I created a new username called user01. Then, I used usermod to grant permissions with another user.
After that, I logged out and login as user 02 but can access to /home/user01
[user02#SRV01 ~]$ cd /home/user01/
-bash: cd: /home/user01/: Permission denied
I checked the directory and permisions of /home/user01 and user by this commands:
[user02#SRV01 ~]$ ls -ltrh / | grep home
drwxr-xr-x. 10 root root 4,0K feb 19 2019 home
[user02#SRV01 ~]$ ls -ltrh /home | grep user01
drwxrwxr-x+ 17 user01 user01 4,0K nov 26 18:14 user01
root#SRV01 /home # id user02
uid=509(user02) gid=500(user01) grupos=500(user01),511(user02)
What's the exactly problem? Thank's in advance
The plus sign at the end in the listing of user01 directory implies the use of ACL. (Access Control Lists)
For more information on the permissions, use getfacl command.
That should show that the user02 has read-execute access on the directory user01.
If the appropriate setting is not there, you'll need to do that using setfacl.
For example,
setfacl -m u:user02:x user01
setfacl -m u:user02:r user01
I hope this works!
You can play around with them after reading more on man page of the getfacl/setfacl commands.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 4 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
Boy howdy, I'm kind of scratching my head over this.
I have a directory with 770 permissions:
inger#server$> ls -ld mydir
drwxrwx--- 2 root mygroup1 4096 May 22 05:27 mydir
I can't cd into it:
inger#server$> cd mydir
-bash: cd: mydir: Permission denied
Hmm, okay, I guess I'm not in the mygroup1 group, right? Wrong:
inger#server$> groups inger
inger: inger [a bunch of other groups] mygroup1 mygroup2 mygroup3
...confirming with getent
inger#server$> getent group mygroup1
mygroup1:*:1903:inger,[a bunch of other users]
...Maybe there's some mixup with the GID of mygroup1? Nope:
inger#server$> ls -nd mydir
drwxrwx--- 2 0 1903 4096 May 22 05:27 mydir
If I chown the group to root:mygroup2, I can get in just fine:
inger#server$> sudo -s
root#server:# chown root:mygroup2 mydir
root#server:# ls -ld mydir
drwxrwx--- 2 root mygroup2 4096 Aug 15 09:44 mydir
root#server:# exit
inger#server$> cd mydir
^^ that works
There are no special ACLs overriding normal UNIX perms:
inger#server$> getfacl mydir
# file: mydir
# owner: root
# group: mygroup1
user::rwx
group::rwx
other::---
This directory doesn't have a special NFS mount or anything - it shares a mount with other directories, none of which have this problem, but they also aren't owned by mygroup1.
So, the problem appears to be specific to this group.
This problem was discovered this morning - members of mygroup1 could get into mydir just fine yesterday.
We manage users and groups with FreeIPA, and yesterday I added some new users to the mygroup1 group. But I added users to the mygroup2 group as well, and there are no problems with that.
Anyone have any recommendations?
This is a limitation with certain NFS configurations where your group memberships after the 16th group are ignored when resolving permissions. Here is a good writeup on it.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Simple question: I have a user called "user" on my system. This user has sudo privileges. Why can't I browse into the sudoer.d directory then?
Is it because cd is a built-in command?
[user#localhost etc]$ ls -al | grep sudoers.d
drwxr-x---. 2 root root 4096 Apr 4 18:09 sudoers.d
[user#localhost etc]$ sudo cd sudoers.d
[user#localhost etc]$ pwd
/etc
[user#localhost etc]$ sudo ls -la sudoers.d/
total 12
drwxr-x---. 2 root root 4096 Apr 4 18:09 .
drwxr-xr-x. 79 root root 4096 May 5 05:20 ..
-r--r-----. 1 root root 33 Apr 4 18:09 vagrant
[user#localhost etc]$ sudo vim sudoers.d/vagrant
[user#localhost etc]$
Thanks a lot.
It happens because sudo simply executes the command executable you pass to it with elevated privileges, and forwards the rest of arguments. Since cd is a shell builtin, sudo won't find the file to execute, which results in an error.
If you wish to have an interactive shell with elevated privileges, use sudo su
sudo opens a new shell. That shell changes its working directory. And then it exits. The original shell's working directory is never changed, nor can it be.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
On Ubuntu 12.04, the chown command doesn't seem to be working like it should
root#server:/var/www/folder/# ls -al
Running this puts out
drwxr-xr-x 11 776 sftponly 4096 Feb 17 14:08 Other_Folder
I need write permissions for the group, so I run:
chown -R 776 ./Other_Folder
Then when I run ls -al again, the output is still
drwxr-xr-x 11 776 sftponly 4096 Feb 17 14:08 Other_Folder
chown is used to change ownership of the file, not change permissions.
ls -al is not showing you who owns the file, just its permissions.
If root owns those files, you'll need to chown them properly, before you can change their permissions:
chown -R yourname:yourname folderName
Then as the owner you can change their permissions:
chmod -R 776 folderName
Edit:
I double checked the syntax and it seems to be right, you'll likely need to use sudo to use them.