Sponsored Content
Operating Systems AIX IBM TDS/SDS (LDAP) - can I mix endianness among servers in an instance ? Post 303039513 by maraixadm on Tuesday 8th of October 2019 02:55:13 PM
Old 10-08-2019
Smilie yep. I figured if someone has blazed this trail before I'd sponge off their work. I'll update here with results.
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

HP-UX 10.2 servers interoperability with IBM mass storage devices

Does anyone have succesfully interconnected HP-UX 10.2 HP 9000 K370 servers with A6885A HBA's, with an IBM Fastt storage server? I need to replace integrate both platforms. Interoperability matrices from manufacturers do not certified such integration. Thanks for anybody's help. (0 Replies)
Discussion started by: raltmannr
0 Replies

2. UNIX for Dummies Questions & Answers

Is no LDAP unusual for 40+ solaris servers?

I am the new jr admin on a solaris team (2 people). We have over 40 solaris servers (v8 and v9) yet no LDAP to manage it all. Is this unusual? So, if we need to add a new user, we have to add him 40x. Thanks in advance ~R (1 Reply)
Discussion started by: abstractrick
1 Replies

3. AIX

IBM Servers Documentation

Hello dear friends, I wanrt to document our servers configuration but have no Idea which softweare should I use for documenting server environment.. maybe anyone can suggest me which software should I use.. thanks in Advance (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies

4. AIX

executable problems with shell script in IBM servers

We have a java stand alone application running currently on sun Solaris system. The java application runs on Jdk 1.4. We are reshooting this java application to new Ibm servers. There are 10 unix scripts for this application. All scripts works well except one shell script, This shell... (2 Replies)
Discussion started by: poojagupta
2 Replies

5. AIX

Mix LDAP and LOCAL user on AIX

Hello, I'm currently trying to mix local and LDAP users on an AIX 7.1. I've triied many things. My LDAP Server in on a CentOS - OpenLDAP (which works fine with linux). I'm currently stuck on AIX at how to declare LDAP AND Local users. Here's what i did : /usr/sbin/mksecldap -c -h 'ldap03'... (15 Replies)
Discussion started by: AIX_user_324891
15 Replies
auditd(1m)																auditd(1m)

NAME
auditd - Starts the DCE Audit Daemon. SYNOPSIS
auditd [-t trail_file] [-a] [-s size] [-wrap] [-w svc_route] [-d debug_level] OPTIONS
Specifies the pathname of the audit trail file used by the Audit daemon. The default path of the audit trail file is dcelo- cal/var/aud/adm/central_trail. If an audit trail file name (instead of an absolute pathname) is specified, the file will be created in the dcelocal/var/aud/adm/ directory. Audits the Audit daemon's control interface access. Sets a warning threshold on the size of the audit trail file. The Audit daemon displays a warning message each time an audit record is appended to the audit trail after the threshold has been reached. Wraps the recording of audit events to the beginning of the audit trail file when its size limit is reached. The default action when the size limit has been reached is to stop auditing. Specifies where each level of serviceability messages are routed. The svc_route argument is divided into three fields, separated by colons - the level, a routing identifier, and a routing parameter: severity:how:where See svcroute(5) for possible values for these fields. Specifies debugging level of sub-components. The debug_level argument contains four fields separated by a colon: component:flags:how:where See svcroute(5) for possible values of these fields. DESCRIPTION
The auditd command starts the Audit daemon. The Audit daemon must be run on the host before the audit clients. The Audit daemon can only service audit clients that are on the host where it is running. Thus, an Audit daemon must be installed and run on every host in the cell that has audit clients (audit clients include DCE servers and user-written application servers). The Audit daemon has two functions. It maintains the filter files which are shared by all audit clients running on the host. It also pro- vides an audit record logging service to these clients. The Audit daemon runs under the local host's machine principal identity (host/hostname/self). A DCE Host daemon (dced) must be running on the local host when auditd is started. Typically, dced and auditd are started at boot time. The auditd process places itself in the background and sends messages indicating it is ready to service requests for updating or querying filters and logging audit records. Privileges Required You must be logged into a privileged account (cell_admin or a member of the audit-admin group) to be able to run auditd. EXAMPLES
The following example starts the Audit daemon using the default audit trail file (dcelocal/var/aud/adm/central_trail): $ auditd The following example starts the Audit daemon and specifies my_trail_file as the audit trail file. $auditd -t my_trail_file The following example starts the Audit daemon and specifies where each level of serviceability messages is going to be routed. $ auditd -w FATAL:FILE:/dev/console -w NOTICE:FILE:/opt/dcelocal/var/audit/adm/svc_log The following example starts the Audit daemon and specifies the debugging level. $ auditd -d 1,esl.9 RELATED INFORMATION
aud(1m), audevents(1m), audfilter(1m), audtrail(1m), dcecp(1m). auditd(1m)
All times are GMT -4. The time now is 09:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy