03-05-2009
what impact root gid changed from other to root is?
> id root
0(root) 1(other)
From CIS scanning result"it should make sure the root's gid is equal to 0", so I don't know what's the impact for that change to whole system? BTW, why is there a group named other under solaris? what does group "other" do ?
Thanks very much!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
All,
I want to run a non-root script as the root user with non-root environment variables with crontab. The non-root user would have environment variables for database access such as Oracle or Sybase. The root user does not have the Oracle or Sybase enviroment variables. I thought you could do... (2 Replies)
Discussion started by: bubba112557
2 Replies
2. Solaris
Hi All,
I have changed the shell of the root accidentally to /sbin/bash :mad:
How do I change that? :(
To change that I need to go to ok prompt I think, and there I need to mount the root file system in order to make changes to the respective file.
Can any one please suggest how do I do... (4 Replies)
Discussion started by: pintu_asim
4 Replies
3. SuSE
The group of the /root folder has been changed and then logged out
I am not able to log in to the /root user as it is saying Xsession log in not allowed
Is there any way that the group of the /root folder be changed? (1 Reply)
Discussion started by: napster_san
1 Replies
4. UNIX for Advanced & Expert Users
Hi Experts,
I have create a new user with uid and gid as 0 in SuSE-11 Server. After that all the files having root owner ship are showing as new user name as owner. If I login as root, and type 'id' command, it also shows the new user.
Sample output from my server.
host:~ # id
uid=0(test)... (4 Replies)
Discussion started by: vipinable
4 Replies
5. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
6. Solaris
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I was carrying out some simple admin tasks setting up a user, logged in as root when I fumbled on the keyboard. It appears I typed
cp * ../user/<esc><esc>I hit return and now the display has set to a strange array of symbols
e.g.
¼Ùïõò §ÏÅÎÓÓȧ ãïîîåãôéïî èáó ôåòíéîáôåä
I've tried looking at the... (7 Replies)
Discussion started by: becky492
7 Replies
8. Shell Programming and Scripting
I need to list users in /etc/passwd with root's GID or UID or /root as home directory
If we have these entries in /etc/passwd
root:x:0:0:root:/root:/bin/bash
rootgooduser1:x:100:100::/home/gooduser1:/bin/bash
baduser1:x:0:300::/home/baduser1:/bin/bash... (6 Replies)
Discussion started by: anil510
6 Replies
9. AIX
Hello
i am running AIX 6.1. i recently changed the root password using passwd and pwdadm. while the new password works fine, i am still able to login using the old password. is there anyway this can disabled\fixed
thanks (5 Replies)
Discussion started by: dnlsingh
5 Replies
10. UNIX for Dummies Questions & Answers
I had a question in my test which asked where suppose user B has a program with 's' bit set. Can user A run this program and gain root privileges in any way?
I suppose not as the suid program run with privileges of owner and this program will run with B's privileges and not root. (1 Reply)
Discussion started by: syncmaster
1 Replies
LEARN ABOUT OPENSOLARIS
group
group(4) File Formats group(4)
NAME
group - group file
DESCRIPTION
The group file is a local source of group information. The group file can be used in conjunction with other group sources, including the
NIS maps group.byname and group.bygid, the NIS+ table group, or group information stored on an LDAP server. Programs use the getgrnam(3C)
routines to access this information.
The group file contains a one-line entry for each group recognized by the system, of the form:
groupname:password: gid:user-list
where
groupname The name of the group. A string consisting of lower case alphabetic characters and numeric characters. Neither a colon (:) nor
a NEWLINE can be part of a groupname. The string must be less than MAXGLEN-1, usually 8, characters long.
gid The group's unique numerical ID (GID) within the system.
user-list A comma-separated list of users allowed in the group.
The maximum value of the gid field is 2147483647. To maximize interoperability and compatibility, administrators are recommended to assign
groups using the range of GIDs below 60000 where possible.
If the password field is empty, no password is demanded. During user identification and authentication, the supplementary group access list
is initialized sequentially from information in this file. If a user is in more groups than the system is configured for, {NGROUPS_MAX}, a
warning will be given and subsequent group specifications will be ignored.
Malformed entries cause routines that read this file to halt, in which case group assignments specified further along are never made. To
prevent this from happening, use grpck(1B) to check the /etc/group database from time to time.
If the number of characters in an entry exceeds 2047, group maintenance commands, such as groupdel(1M) and groupmod(1M), fail.
Previous releases used a group entry beginning with a `+' (plus sign) or `-' (minus sign) to selectively incorporate entries from a naming
service source (for example, an NIS map or data from an LDAP server) for group. If still required, this is supported by specifying
group:compat in nsswitch.conf(4). The compat source may not be supported in future releases. Possible sources are files followed by ldap or
nisplus. This has the effect of incorporating information from an LDAP server or the entire contents of the NIS+ group table after the
group file.
EXAMPLES
Example 1 Example group File.
The following is an example of a group file:
root::0:root
stooges:q.mJzTnu8icF.:10:larry,moe,curly
and the sample group entry from nsswitch.conf:
group: files ldap
With these entries, the group stooges will have members larry, moe, and curly, and all groups listed on the LDAP server are effectively
incorporated after the entry for stooges.
If the group file was:
root::0:root
stooges:q.mJzTnu8icF.:10:larry,moe,curly
+:
and the group entry from nsswitch.conf:
group: compat
all the groups listed in the NIS group.bygid and group.byname maps would be effectively incorporated after the entry for stooges.
SEE ALSO
groups(1), grpck(1B), newgrp(1), groupadd(1M), groupdel(1M), groupmod(1M), getgrnam(3C), initgroups(3C), nsswitch.conf(4), unistd.h(3HEAD)
System Administration Guide: Basic Administration
SunOS 5.11 27 Aug 2008 group(4)