03-20-2007
X2100 AMD server
I am having a problem getting info from the x2100 servers running solaris 10. I can get things like (ls,cd) and so on but if i use the vi command the logs doesn't tell me what file the user has opened or (vi) at the time.
I wonder if it's a problem with the x2100 os artch or maybe some extra config that i have to do to fix it. I am using the excat same config on my test Sun e250 and that is working just fine.
Help please.
Thanks
10 More Discussions You Might Find Interesting
1. Solaris
I'm looking for a software to capture my systems logs, and bsm (basic security module) logs to centralise the administration. Do you have a suggestions. Opensource or not. (6 Replies)
Discussion started by: simquest
6 Replies
2. Programming
I have a C program and want to write messages to a log. BSM is being used for O/S auditing. Can I write my messages to the BSM log? If so, how do I do that? I'm not finding any API's for that. Any URLs, samples, guidance would be appreciated. (0 Replies)
Discussion started by: JDO
0 Replies
3. Solaris
I got a lot of this message in my /var/audit log
how can I exclude this message?
header,127,2,invalid event number,fe,hostsol1.com.sg,2007-12-21 00:10:01.001 +08:00,argument,1,0x5,processor ID,argument
,2,0x3,flag,text,P_STATUS,subject,zhang1,root,root,root,root,18228,576129155,291 131094... (1 Reply)
Discussion started by: geoffry
1 Replies
4. Solaris
How do I setup audit to alert on write conditions for individual files? Thanks. (3 Replies)
Discussion started by: dxs
3 Replies
5. Solaris
Hello,
I was wondering when Solaris auditing is enabled, If it is possible to keep track of users that are allowed to sudo to root. In other words, I would like to know which user did what on my Solaris box. (assumig that user can "sudo su -" )
Thanks. (2 Replies)
Discussion started by: niyazi
2 Replies
6. Solaris
Let me preface with I am semi-new to Solaris. I work with it in the labs at work and that's about my extent (although I run Linux at home).
Well, a week ago security comes around with updated requirements, some of which are the need to audit all failures. For the life of me I cannot get a... (0 Replies)
Discussion started by: mph275
0 Replies
7. Solaris
Hi ,
I don't want logs from a particular "library" to get recorded in the audit.log file. Is that possible with BSM? Please guide.
Thanks. (2 Replies)
Discussion started by: chinchao
2 Replies
8. Solaris
New to Solaris in general (coming from a RHEL background) I'm trying to enable auditing on the system with the following in /etc/security/audit_control:
But there are two areas where it seems to break with expected behavior (maybe it's poor expectations on my part):
1) it seems to be... (0 Replies)
Discussion started by: thmnetwork
0 Replies
9. Solaris
Hi all,
I'm trying to read Solaris BSM log in user friendly form. Found old tools including bsmparser java tool and php code. But none of them working. What are you using for parsing BSM log? (2 Replies)
Discussion started by: sembii
2 Replies
10. Solaris
Hello,
Im glad to become a member of this forums,
Im new on solaris and recentrly im introducing to use auditing service in that system.
The need is, that I need how to exclude a directory to the audit service not audit it.
And, a plus, I need of how to disable auditing the root user in... (0 Replies)
Discussion started by: sysh4ck
0 Replies
LEARN ABOUT DEBIAN
slaptest
SLAPTEST(8) System Manager's Manual SLAPTEST(8)
NAME
slaptest - Check the suitability of the OpenLDAP slapd configuration
SYNOPSIS
/usr/sbin/slaptest [-d debug-level] [-f slapd.conf] [-F confdir] [-ndbnum] [-o option[=value]] [-Q] [-u] [-v]
DESCRIPTION
Slaptest is used to check the conformance of the slapd(8) configuration. It opens the slapd.conf(5) configuration file or the slapd-con-
fig(5) backend, and parses it according to the general and the backend-specific rules, checking its sanity.
OPTIONS
-d debug-level
enable debugging messages as defined by the specified debug-level; see slapd(8) for details.
-f slapd.conf
specify an alternative slapd.conf(5) file.
-F confdir
specify a config directory. If both -f and -F are specified, the config file will be read and converted to config directory format
and written to the specified directory. If neither option is specified, slaptest will attempt to read the default config directory
before trying to use the default config file. If a valid config directory exists then the default config file is ignored. If dry-run
mode is also specified, no conversion will occur.
-n dbnum
Just open and test the dbnum-th database listed in the configuration file. To only test the config database slapd-config(5), use -n
0 as it is always the first database.
-o option[=value]
Specify an option with a(n optional) value. Possible generic options/values are:
syslog=<subsystems> (see `-s' in slapd(8))
syslog-level=<level> (see `-S' in slapd(8))
syslog-user=<user> (see `-l' in slapd(8))
-Q Be extremely quiet: only the exit code indicates success (0) or not (any other value).
-u enable dry-run mode (i.e. don't fail if databases cannot be opened, but config is fine).
-v enable verbose mode.
EXAMPLES
To check a slapd.conf(5) give the command:
/usr/sbin/slaptest -f //etc/ldap/slapd.conf -v
SEE ALSO
ldap(3), slapd(8), slapdn(8)
"OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
ACKNOWLEDGEMENTS
OpenLDAP Software is developed and maintained by The OpenLDAP Project <http://www.openldap.org/>. OpenLDAP Software is derived from Uni-
versity of Michigan LDAP 3.3 Release.
OpenLDAP 2012/04/23 SLAPTEST(8)