10-07-2010
Everyone that logs in, every command with user id and time(s)? That's a lot of writing for a modified kernel where exec is logging. I heard of a recovery system where they substituted a custom /lib/libc.* so all apps called their exec*() routines, which logged and then called the real exec*() routines by number using system() (ditto for open, read, write, seek, ... so they could restart processing).
Which IP is a different log of who logs in from where, when on what tty. What do you want to do with things run by cron, at, daemon servers, root and his buddies?
What happens if the log disk fills?
There are stats for command use, but I forget where.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I am new to unix OS.
Commands(external commands) given by the user are examined by shell and later executed by kernel.
Now I want to know how the internal(built in) commands are executed.
Please clarify whether they are executed directly by shell or by kernel.
Thanks in... (2 Replies)
Discussion started by: chaitra
2 Replies
2. Shell Programming and Scripting
Hi,
I have executed a set of commands on the linux server and later rebooted the server. Is it possible to get the details of the commands I executed prior to the reboot? If yes please let me know how?
Thanks. (1 Reply)
Discussion started by: yoursdavinder
1 Replies
3. Shell Programming and Scripting
Dear friends,
Whenever I do logout from a session initiated by ssh/su, I need to print a small report which says the login time, logout time, commands got executed..
How can it be done?
I know when doing ssh, .profile file will get executed. Shall we do something with the help of it. (1 Reply)
Discussion started by: nagalenoj
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
how to overcome this warning issue.
code:
#echo 'ls > /home/rxcprod/a.out' | at -q a now
warning: commands will be executed using /usr/bin/sh
job 1318943704.a at Tue Oct 18 09:15:04 2011 (4 Replies)
Discussion started by: tushar_spatil
4 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have cleared the commands by using >$HOME/.sh_history.
But if i issue HISTORY it shows some reference numbers but not the commands executed.
But i want to truncate those line numbers too.
May i know how i can achieve this?
Thanks (1 Reply)
Discussion started by: pandeesh
1 Replies
6. Debian
Hi,
I've been looking for a way to execute a console program (is in windows but by now I accept the linux way) from a linux machine, but this program has to be opened in the remote side. Linux machine acts only as a "signaling" host. My program has to open the camera in the remote side, but only... (7 Replies)
Discussion started by: zauberberg
7 Replies
7. Shell Programming and Scripting
Hi All,
Need to run the netstat -i command on the list of hosts and check if "Ierrs" and "Oerrs" has value greaterthan 0.
for Ex: below output, driver bge1 and bge3 has Oerrs and Ierrs value > 0, So, script should report saying
"Netstat status for $host, driver bge1 has Oerrs = 20, Failed"... (5 Replies)
Discussion started by: Optimus81
5 Replies
8. Shell Programming and Scripting
Geeks,
Could you please help me out in my script and identify the missing piece. I need to check/get the exit status of a remote command executed on remote host through script and send out an email when process/processes is/are not running on any/all server(s).
Here's the complete... (5 Replies)
Discussion started by: lovesaikrishna
5 Replies
9. Solaris
Am trying to copy a tar file onto a series of remote hosts and untar it at the destination. Need to do this without having to do multiple ssh.
Actions to perform within a single ssh session via shell script
- copy a file
- untar at destination (remote host)
OS : Linux RHEL6 (3 Replies)
Discussion started by: sankasu
3 Replies
10. Shell Programming and Scripting
Hi all,
i'm trying to gether multiple pattern on remote hosts, and trying to print hostname and the pattern,
ssh remoteserver1 -C 'hostname 2>&1;cat /var/log/server1.log | awk -F ";" '"'"'{ print " "$2" "$5}'"'"'| sort | uniq -c | sort -g -r '
The output is the following,
remoteserver1
... (8 Replies)
Discussion started by: charli1
8 Replies
vxiod(7) Miscellaneous Information Manual vxiod(7)
NAME
vxiod - Veritas Volume Manager I/O daemon process control device
DESCRIPTION
The vxiod device in Veritas Volume Manager (VxVM) is used to control the number of volume I/O daemons active on the system. A process con-
text is necessary to implement the plex consistency recovery and writeback error handling policies for multi-plex volumes, and for continu-
ing normal I/O after a log write if the volume has logging enabled. It is also required for the plex recovery performed with a mirrored
volume in the read/writeback mode.
There are three aspects of I/O daemon operations:
o General I/O
o Error handling
o Log handling
I/O handling is achieved by an ioctl command that does not return, but instead calls the vxiod routine to wait for errors or I/O requests
and process them. When an error occurs, if there are no I/O daemons active, the I/O simply turns into a failure on that plex. If a gen-
eral I/O request is queued up when no daemons exist, then the I/O will hang forever until a daemon process is created. If I/O daemons are
active, then the I/O is put on a work queue and the daemons are awakened. A daemon takes an error request and tries to read other plexes
until a read succeeds or all plexes have been tried. Then, if the writeback facility is enabled, the daemon tries to write the good data
to each plex that failed on the read. If the write is successful, the read error is nullified. An I/O request is handled in a similar
manner.
Logging is handled in a similar manner. An ioctl command, which does not return, is issued to create a daemon for each volume which has
logging enabled. This daemon monitors two queues: one queue of I/O which was started while the log was busy (the ``log'' queue), and
another queue of requests which have been logged and now need to be started (the ``ready'' queue). I/O requests are taken from the log
queue when the log is no longer busy, and another log write is started. Completion of a log write results in all I/O requests which have
just been logged being placed on the I/O daemon's ready queue where they are immediately started.
One mechanism finds out how many I/O error daemons are running, and another mechanism allows a process to become an I/O daemon. Before a
process becomes an I/O daemon, it should close all open files and detach from the controlling tty. An I/O or logging daemon cannot be
killed except through an explicit ioctl.
FILES
/dev/vx/iod vxiod control device
SEE ALSO
vxiod(1M), ioctl(2)
VxVM 5.0.31.1 24 Mar 2008 vxiod(7)