12-19-2007
I don't see port for sysstat, but the binaries inside should be pre-installed on OpenBSD, according to some articles on the net.
3 More Discussions You Might Find Interesting
1. Red Hat
I am looking for an alternative for sudo in linux, where i need not type the password.
OR is there any other version of 'growisofs', which can be executed under sudo??? As currently 'growisofs' refuses to start under sudo...
Thanks in advance (12 Replies)
Discussion started by: sony star
12 Replies
2. Red Hat
I have installed version of ntop 4.0.3 by guide.
But I can't start ntop daemon/service. I didn't find a service file for starting.
During the installation there was no problem only want to RRDTool so I installed that. Now there is no necessary package required.
I didn't find in /etc/init.d/... (9 Replies)
Discussion started by: getrue
9 Replies
3. Cybersecurity
I have been asked to place 2 (1 NTOP & 1 SNORT) boxes within our network as part of our tool kit for network monitoring and Intrusion detection. Out network is very simplistic and it layed out like this:
internet
|
|
Cisco 1811 Router (8x Layer 2 switch ports)
... (0 Replies)
Discussion started by: metallica1973
0 Replies
LEARN ABOUT OPENDARWIN
issetugid
ISSETUGID(2) BSD System Calls Manual ISSETUGID(2)
NAME
issetugid -- is current executable running setuid or setgid
SYNOPSIS
#include <unistd.h>
int
issetugid(void);
DESCRIPTION
The issetugid() function returns 1 if the process was made setuid or setgid as the result of the last execve() system call. Otherwise it
returns 0.
This system call exists so that library routines (inside libc, libtermlib, or other libraries) can gaurantee safe behavior when used inside
setuid or setgid programs. Some library routines may not be passed sufficient information to know if the current program was started setuid
or setgid because higher level calling code may have made changes to the uid or the euid. In particular, it is wise to use this call to
determine if a pathname returned from a getenv() call may safely be used to open() the specified file.
issetugid() is unaffected by calls to setuid(), fork(), and other such calls. It is only controlled by execve().
ERRORS
The issetugid() function is always successful, and no return value is reserved to indicate an error.
SEE ALSO
execve(2), setuid(2), seteuid(2,) setgid(2), setegid(2)
HISTORY
A lstat() function call appeared in OpenBSD 2.0
OpenBSD 2.0 August, 25 1996 OpenBSD 2.0