How to list group members in solaris 9 Post: 302311961

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

listing members of a unix group

I know there is a "groups" command to list the groups a user belongs to, but how about the opposite? Is there a standard command to find out which users belong to a particular group?

2. Solaris

How do you list users in a solaris group

I need to list all users in a group. This is a large unix site running nis+.

3. Solaris

make issue when I add some members into a NIS group on solaris 9,please help !!

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. Programming

allowing members of a group to kill a process

I've written a python program where I want to allow members of a specific group the ability to kill it, and I'm not sure how to do it. I've been looking at the setuid() and setgid() and similar functions in the os module, but haven't been able to get them to work. I can't seem to change the uid or...

5. Shell Programming and Scripting

How to get a list of group members?

Is there a command to get a list of group members? Something similar to the groups command, but instead of passing a username and returning groups, you pass it a groupname, and it returns members? It is difficult to do it manually because the group membership information is split across two...

6. AIX

How to allow group members to kill process?

Hey I'm writing a script that creates some processes,and some scripts which kill those processes. the question is Simply: How can I allow group members to be able to kill processes created by other member at the same group? I need your help as soon as possible Thanks for your help in...

7. Linux

members in a group

Hi all, I am new to Linux.Can anyone tell me how to display or list all the members in a group? Thanks in advance.

8. UNIX for Advanced & Expert Users

Setfacl and granting permissions to a group and its members on a directory

Hi! I created a group HACKERS and made the user "demo" its member. $ id demo uid=500(demo) gid=500(demo) groups=500(demo),502(HACKERS) $ Next, I granted read and execute permissions to the group "HACKERS" on /var/log/httpd as shown below: setfacl -m "g:HACKERS:r-x"...

LEARN ABOUT DEBIAN

wdmd

WDMD(8) 						      System Manager's Manual							   WDMD(8)

NAME

       wdmd - watchdog multiplexing daemon

SYNOPSIS

       wdmd [OPTIONS]

DESCRIPTION

       This  daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done.  Every test interval
       (10 seconds), the daemon tests each source.  If any test fails, the KEEPALIVE is not done.  In a standard configuration, the watchdog timer
       will  reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout").	This means that if single test fails 5-6 times in row, the
       watchdog will fire and reset the system.  With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.

       T seconds, P pass, F fail
       T00: test1 P, test2 P, test3 P: KEEPALIVE done
       T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
       T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
       T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
       T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
       T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
       T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
       T60: watchdog fires, system resets

       (Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)

       A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog	is
       guaranteed  to fire, regardless of whether other sources on the system have passed or failed.  A spurious reset due to the combined effects
       of multiple failing tests as shown above, is an accepted side effect.

       wdmd will exit if a watchdog driver is not loaded.

       wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).

   Test Source: clients
       Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
       Every test interval, wdmd will check if the expiry time for a connection has been reached.  If so, the test for that client fails.

       (Other test sources such as scripts executed each test interval may be added in the future.)

OPTIONS

       -D     Enable debugging to stderr and don't fork.

       -H num Enable (1) or disable (0) high priority features such as realtime scheduling priority and mlockall.
	      Default 1.

								    2011-08-01								   WDMD(8)