10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi, How to pull netgroup from all servers
I think the netgroup resides in /etc/security/access.conf so I want to know how to get the list of netgroup in all the servers.
I have a jump server I can run the script from there to get the list but not sure how to do the script. Any ideas or... (1 Reply)
Discussion started by: dbashyam
1 Replies
2. UNIX for Advanced & Expert Users
I'm considering the merits of slightly redefining the "domain" field in a NIS netgroup (the third field in the triple) to make it more useful, in a new Internet Draft that I am currently developing. Does anyone out there who uses NIS actually make use of the "domain" field? The places I've worked... (8 Replies)
Discussion started by: cambridge
8 Replies
3. UNIX for Dummies Questions & Answers
I have root access on a linux (RH5.4) server within an NIS setup that I don't control. I have an NIS account that creates directories on my local node that I want to be writable by my local apache account.
The NIS account is only a member of the "users" group and the local apache account is... (1 Reply)
Discussion started by: clindseysmith
1 Replies
4. Linux
Hi there,
I am trying to set a ulimit max in the /etc/security/limits.conf against a NIS netgroup (which contains a whole bunch of users) instead of a local user or group.
so I have a NIS netgroup called +@myusers , none of whose users are defined locally on the box. I want to ensure that... (2 Replies)
Discussion started by: rethink
2 Replies
5. UNIX for Advanced & Expert Users
I'm running a NIS on an network of Ubuntu 8.04 linux systems. I'm seeing a weird problem where the 'id' command is not returning all the groups I am a member of. For example:
alex@client $ id -Gn
localgroupA localgroupB nisgroup1 nisgroup2 nisgroup4
alex@client $ id -Gn alex
nisgroup1... (0 Replies)
Discussion started by: vertigo23
0 Replies
6. Solaris
Hello experts.
I am using Solaris10. How can i allow a group of users, remaining should be deny.
Thanx in advance. (9 Replies)
Discussion started by: younus_syed
9 Replies
7. Solaris
Hello Sir,
I want to add some members into a group on NIS domain, but when I run "/usr/ccs/bin/make group" to update the group map it was failed :-(
the error message is :
problem storing develop... (4 Replies)
Discussion started by: lk74612
4 Replies
8. UNIX for Advanced & Expert Users
We have a RedHat 8.0 NIS master, with a RedHat 8.0 NIS Slave.
We also have a small number of SUSE 9.1 and SUSE 10 machines here for evaluation.
However, no matter what i do, the SUSE machines will not talk to the NIS Servers.
If i broadcast for NIS Servers for the specified NIS domain, it... (1 Reply)
Discussion started by: fishsponge
1 Replies
9. UNIX for Dummies Questions & Answers
Hi everyone,
I'm new to UNIX so plz excuse me if this sounds foolish
Assume there exists a group 'xyz' on the NIS as well as on the local UNIX box.
And we added the user 'test' to the local group.
Which group priveleges will 'test' have?
do reply..
thanks,
VJ. (3 Replies)
Discussion started by: vjsony
3 Replies
10. UNIX for Advanced & Expert Users
Hi@all,
I'd setup a nis server and 4 slaves. Update of passwd work's fine, but if i create a netgroup file the make all process hang by push the netgroup file.
I work with AIX 4.3.3.0 and Maintance Level 5.
Tank's for help (1 Reply)
Discussion started by: Michael
1 Replies
GROUP(5) BSD File Formats Manual GROUP(5)
NAME
group -- format of the group permissions file
DESCRIPTION
The group file /etc/group is the local source of group information. It can be used in conjunction with the Hesiod domain 'group', and the
NIS maps 'group.byname' and 'group.bygid', as controlled by nsswitch.conf(5).
The group file consists of newline separated ASCII records, usually one per group, containing four colon ':' separated fields. Each line has
the form:
group:passwd:gid:[member[,member]...]
These fields are as follows:
group Name of the group.
passwd Group's encrypted password.
gid The group's decimal ID.
member Group members.
The group field is the group name used for granting file access to users who are members of the group.
The gid field is the number associated with the group name. They should both be unique across the system (and often across a group of sys-
tems) since they control file access.
The passwd field is an optional encrypted password. This field is rarely used and an asterisk is normally placed in it rather than leaving
it blank.
The member field contains the names of users granted the privileges of group. The member names are separated by commas without spaces or
newlines. A user is automatically in a group if that group was specified in their /etc/passwd entry and does not need to be added to that
group in the /etc/group file.
Very large groups can be accommodated over multiple lines by specifying the same group name in all of them; other than this, each line has an
identical format to that described above. This can be necessary to avoid the record's length limit, which is currently set to 1024 charac-
ters. Note that the limit can be queried through sysconf(3) by using the _SC_GETGR_R_SIZE_MAX parameter. For example:
biggrp:*:1000:user001,user002,user003,...,user099,user100
biggrp:*:1000:user101,user102,user103,...
The group with the name ``wheel'' has a special meaning to the su(1) command: if it exists and has any members, only users listed in that
group are allowed to su to ``root''.
HESIOD SUPPORT
If 'dns' is specified for the 'group' database in nsswitch.conf(5), then group lookups occur from the 'group' Hesiod domain.
NIS SUPPORT
If 'nis' is specified for the 'group' database in nsswitch.conf(5), then group lookups occur from the 'group.byname' and 'group.bygid' NIS
map.
COMPAT SUPPORT
If 'compat' is specified for the 'group' database, and either 'dns' or 'nis' is specified for the 'group_compat' database in
nsswitch.conf(5), then the group file may also contain lines of the format
+name:*::
which causes the specified group to be included from the 'group' Hesiod domain or the 'group.byname' NIS map (respectively).
If no group name is specified, or the plus sign (``+'') appears alone on line, all groups are included from the Hesiod domain or the NIS map.
Hesiod or NIS compat references may appear anywhere in the file, but the single plus sign (``+'') form should be on the last line, for his-
torical reasons. Only the first group with a specific name encountered, whether in the group file itself, or included via Hesiod or NIS,
will be used.
FILES
/etc/group
SEE ALSO
newgrp(1), passwd(1), su(1), setgroups(2), crypt(3), initgroups(3), nsswitch.conf(5), passwd(5), yp(8)
HISTORY
A group file format appeared in Version 6 AT&T UNIX.
The NIS file format first appeared in SunOS.
The Hesiod support first appeared in NetBSD 1.4.
BUGS
The passwd(1) command does not change the group passwords.
BSD
June 21, 2007 BSD