12-08-2011
bash logging al $() command lines
I have been doing a lot more bash on LINUX RedHat and Ubuntu lately, and one thing keeps cropping up intermittently. If I do a $( some-commands ) Command Substitution, the some-commands are logged onto my screen each time they are evaluated. Did I turn on some odd option? It seems to happen just some times.
Last edited by DGPickett; 12-08-2011 at 03:18 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all...
I've completed the task of deploying SSH over my 400 servers.
I don't know if i'm right or wrong, but ssh doesn't do any command-logging, does it?
Is there a app i can use to log all commands passed ( besides the usual .sh_history), whith no modification possible by the user, and how... (2 Replies)
Discussion started by: penguin-friend
2 Replies
2. UNIX for Dummies Questions & Answers
Hi, I am trying to recollect the command used to log a file.
We use this command just before starting, say, installation. At the end you get a file capturing the series of commands you used during the course of time and sytems response.
Could anybody please help.
Thanks,
Dasa (3 Replies)
Discussion started by: dtamminx
3 Replies
3. Solaris
Does anyone have a simple method of logging all shell commands typed by a user (csh in our case)?
- I could enable auditing, but this would be overkill
- I could enable process accounting, but AFAIK, this does not log arguments
Thanks all. (2 Replies)
Discussion started by: minkie
2 Replies
4. Cybersecurity
I am looking for a really good command logging tool to improve the auditing of my servers. I have previously used snoopy but this is currently a bit flaky and causing serious problems for me, it doesn't look like it's been maintained since 2004, it didn't even want to compile until I added -fPIC... (1 Reply)
Discussion started by: humbletech99
1 Replies
5. Shell Programming and Scripting
Hi.
I have the script shown below. If I execute it form the command line it seems to work properly, but when I fun it using the unix "at" command
"at -m now < ./kill-at-job.sh"
It appears to hang. Below is the script, the input file, and the execution as reported in the e-mail from the "at"... (3 Replies)
Discussion started by: jbsimon000
3 Replies
6. Shell Programming and Scripting
I'm looking at allowing remote telnet into my server.
like any security-minded administrator, I want to log what my users type on the telnet session.
I'm using the script command to generate transcripts of the users session.
I have /etc/profile set to automatically start the script command... (2 Replies)
Discussion started by: ramnet
2 Replies
7. Shell Programming and Scripting
Is it possible to store all standard-out of a bash script and the binaries it calls in a log file AND still display the stdout on screen?
I know this is possible to store ALL stdout/stderr of a script to a single log file like:
exec 1>&${logFile}
exec 2>&1
But running a script with the... (3 Replies)
Discussion started by: ckmehta
3 Replies
8. Shell Programming and Scripting
HI ,
I have a simple script that moves files from one folder to another folder, I have already done the open-ssh server settings and the script is working fine and is able to transfer the files from one folder to another but right now I myself execute this script by using my creditianls to... (4 Replies)
Discussion started by: nks342
4 Replies
9. Shell Programming and Scripting
I searched the forums for command logging and the user "Driver" seemed to provide a script for logging shell commands with related info like date and time. The subject was "logging command invocations -cmdlog" . I would be interested in this script.
Thanks (0 Replies)
Discussion started by: starcraft
0 Replies
10. Shell Programming and Scripting
BASH Gurus: Anyone know how to append continuous output command appending to a file, but limit that file to no more than 20 lines? The program I have running is simply monitoring my UDP port 53 for incoming packets endlessly. I just need to keep this file from going over 20 lines. Once the file... (3 Replies)
Discussion started by: scorpius2k1
3 Replies
esmd(1M) esmd(1M)
NAME
esmd - Essential Services Monitor (ESM) Daemon
SYNOPSIS
retry_seconds]
DESCRIPTION
The Essential Services Monitor (ESM) daemon, maintains the availability of essential system daemons by automatically restarting them if
they terminate. The ESM daemon monitors the Event Manager daemon, The ESM daemon is started by the init process when the system is ini-
tialized to run level 2 and continues to run until the system is shut down or returned to single user mode. Only one instance of can run
at a time.
Configuration information is sent to the ESM daemon by a control program, which is run at key points in the startup and shutdown proce-
dures. As startup or shutdown progresses, the control program updates the ESM state file, The control program then signals the daemon to
reconfigure itself.
On startup, state transitions occur after has started. On shutdown, transitions occur after each of these monitored daemons has termi-
nated. After each transition, the ESM daemon determines which of the monitored daemons should be running and adjusts its monitoring activ-
ities accordingly.
The ESM daemon reports all state change information, including notice of failures and restarts, through the system logging daemon, syslogd.
Messages are displayed on the system console during periods when syslogd is not running. See syslogd(1M) for more information.
If the ESM daemon fails to restart a monitored daemon, it reports the error by posting a high priority message through syslogd, and makes
no further restart attempts. The system administrator should investigate the problem and restart the failed daemon. The ESM daemon peri-
odically attempts to resume monitoring of the daemon, and posts an informational message when it succeeds. If the monitored daemon fails
again once monitoring has resumed, the ESM daemon again attempts to restart it.
The ESM daemon can be forced to restart a failed daemon by sending a SIGHUP signal to the process.
If there is a need to temporarily disable the ESM daemon for test purposes, in order to prevent the monitored daemons from being restarted
automatically, send a SIGSTOP signal to the process. To reactivate the ESM daemon, send a SIGCONT signal to the process. The ESM daemon
should never be disabled on a production system.
If the ESM daemon is terminated unexpectedly, it is restarted automatically by init.
Options
The command recognizes the following options:
Limit the priority of any syslog messages posted by the ESM daemon to "alert."
If this option is not specified, posts an "emergency" message if it cannot restart a failed daemon. A message may be sent to all
users currently logged in to the system. The option should only be used if the system administrator is actively monitoring syslogd
messages.
Specify the interval between attempts to begin monitoring a daemon
that has failed, and which has been unable to restart automatically. The default period is 30 seconds. Specifying a period of zero
disables retrying.
Notes
To use the start options, you must add them to the startup command in the file. The daemon reports any invalid start options with a single
generic message through syslogd.
Restrictions
The daemon terminates with an error message if it is started by any process other than init.
The /sbin/init.d/esm program is intended to be run by the system startup and shutdown process and should not be run from the command line.
Only one instance of can run at a time.
RETURN VALUE
The following exit values are returned:
0 (Zero) Successful completion.
not 0 An error occurred.
FILES
Executable file
Configuration control script
Initialization process control file
dispatched by boot init
Monitoring state file
Receives esmd status messages
AUTHOR
was developed by Hewlett Packard Company.
SEE ALSO
Commands
kill(1), evmd(1M), init(1M), syslogd(1M).
Files
inittab(4).
esmd(1M)