sg | usermod -g primarygroup username | newgrp | groupmod | gpasswd | chown

By OK -
The primary group is the group applied to you when you log in using the usual methods (TTYs, GUI, SSH, etc.).
Since processes usually inherit the group of the parent, and your initial process or shell would have your primary group as the group, anything you do usually has the effect of the primary group on it (creating files, for example).
The secondary groups are the groups you can start processes as without using a group password, either via sg or to log in to via the newgrp command.

 ubuntu@ubuntu:~/Documents/testadmin$ groups
ubuntu adm cdrom sudo dip www-data plugdev lpadmin sambashare

ubuntu@ubuntu:~/Documents/testadmin$ sg dip 'touch file2'
ubuntu@ubuntu:~/Documents/testadmin$ ll
total 8
drwxrwxr-x 2 ubuntu ubuntu 4096 Dec 11 05:58 ./
drwxr-xr-x 5 ubuntu ubuntu 4096 Dec 11 05:57 ../
-rw-rw-r-- 1 ubuntu ubuntu    0 Dec 11 05:57 file1
-rw-rw-r-- 1 ubuntu dip       0 Dec 11 05:58 file2


ubuntu@ubuntu:~/Documents/testadmin$ sudo usermod -g dip ubuntu
ubuntu@ubuntu:~/Documents/testadmin$ touch file3
ubuntu@ubuntu:~/Documents/testadmin$ ll
total 8
drwxrwxr-x 2 ubuntu dip    4096 Dec 11 06:07 ./
drwxr-xr-x 5 ubuntu dip    4096 Dec 11 05:57 ../
-rw-rw-r-- 1 ubuntu dip       0 Dec 11 05:57 file1
-rw-rw-r-- 1 ubuntu dip       0 Dec 11 05:58 file2
-rw-rw-r-- 1 ubuntu ubuntu    0 Dec 11 06:07 file3
ubuntu@ubuntu:~/Documents/testadmin$ sudo usermod -g ubuntu ubuntu
ubuntu@ubuntu:~/Documents/testadmin$ touch file4
ubuntu@ubuntu:~/Documents/testadmin$ ll
total 8
drwxrwxr-x 2 ubuntu ubuntu 4096 Dec 11 06:07 ./
drwxr-xr-x 5 ubuntu ubuntu 4096 Dec 11 05:57 ../
-rw-rw-r-- 1 ubuntu ubuntu    0 Dec 11 05:57 file1
-rw-rw-r-- 1 ubuntu ubuntu    0 Dec 11 05:58 file2
-rw-rw-r-- 1 ubuntu ubuntu    0 Dec 11 06:07 file3
-rw-rw-r-- 1 ubuntu ubuntu    0 Dec 11 06:07 file4
ubuntu@ubuntu:~/Documents/testadmin$ 


  • newgrp: log into a new group
  • sg: execute a command as a different group ID
  • groupmod: modify a group definition (e.g., the group ID, group name, or password)
  • gpasswd: administer /etc/group and /etc/gshadow files (every group can have administrators, members, and a password)
  • chown or chgrp: change individual or group ownership of a file or directory

Comments

Post a Comment

Popular posts from this blog

HAproxy logging

By OK -
ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log global mode http option httplog option dontlognull         contimeout 5000    
Read more

NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

By OK -
Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availability ssh   ports:   protocols:   masquera
Read more

teamcity Automatic Agent Start under Linux

By OK -
Automatic Agent Start under Linux To run agent automatically on the machine boot under Linux, configure daemon process with the  agent.sh start  command to start it and  agent.sh stop  command to stop it. Refer to an example procedure below: 1. Navigate to the services start/stop services scripts directory: cd /etc/init.d/ 2. Open the build agent service script: sudo vim buildAgent 3. Paste the following into the file : #!/bin/sh ### BEGIN INIT INFO # Provides: TeamCity Build Agent # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start build agent daemon at boot time # Description: Enable service provided by daemon. ### END INIT INFO #Provide the correct user name: USER="agentuser" case "$1" in start) su - $USER -c "cd BuildAgent/bin ; ./agent.sh start" ;; stop) su - $USER -c "cd BuildAgent/bin ; ./agent.
Read more