01-31-2003
Hmmm...
Ah...the classic answer (see my user name)
That is ALWAYS the first place I try....wasnt satisfied with the results. Was hoping to find someone that new of an 'official' site..
thanks though
4 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am looking for some coding standards for Unix Shell Scripting. Can anyone help me out in this?
Regards,
Himanshu (3 Replies)
Discussion started by: himanshu_s
3 Replies
2. Programming
I'm new to UNIX programming. I'm used to starting my program's versions at 1.0, but I look at all the UNIX programs out there and see things like 0.000.1 or 3.3.000 and I'm wondering what these things really mean. Do people just type anything they feel in there? Are things in pre-release... (6 Replies)
Discussion started by: hirni
6 Replies
3. Solaris
Hi All,
Thanks in advance for reading and any posts.
I was wondering if anyone has come across or can recomend or has any security standards that we could implement. We are running production Oracle systems on Solaris 8 boxes (which are global). We are after security considerations... (4 Replies)
Discussion started by: B14speedfreak
4 Replies
4. Programming
Hello Friends,
I am a newbie and have started using different compilers and tools to make myself familiar with their workings. I wanted to know that how compliant is gcc with the C++ standards. It is pretty obvious that no compiler is close to being completely compliant, but if there are some... (7 Replies)
Discussion started by: hthapar
7 Replies
getgid(2) System Calls Manual getgid(2)
NAME
getgid, getegid - Gets the process group ID
SYNOPSIS
#include <unistd.h>
gid_t getgid (void);
gid_t getegid (void);
Application developers may want to specify an #include statement for <sys/types.h> before the one for <unistd.h> if programs are being
developed for multiple platforms. The additional #include statement is not required on Tru64 UNIX systems or by ISO or X/Open standards,
but may be required on other vendors' systems that conform to these standards.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
getgid(), getegid(): POSIX.1, XPG4, XPG4-UNIX
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The getgid() function returns the real group ID of the calling process.
The getegid() function returns the effective group ID of the calling process.
The real group ID is specified at login time. The effective group ID is more transient, and determines additional access permission during
execution of a ``set-group-ID'' process. It is for such processes that the getgid() function is most useful.
RETURN VALUES
The getgid() and getegid() functions return the requested group ID. They are always successful.
RELATED INFORMATION
Commands: groups(1)
Functions: getgroups(2), initgroups(3), setgroups(2), setregid(2)
Standards: standards(5) delim off
getgid(2)