Sponsored Content
Top Forums Shell Programming and Scripting bash logging al $() command lines Post 302580468 by Corona688 on Thursday 8th of December 2011 02:56:04 PM
Old 12-08-2011
Odd.
Code:
echo $-

to see what options you have set in your shell
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SSH and command logging

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

What is command for logging?

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

shell command logging

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

Full Command Logging?

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

Reading lines from a file, using bash, "at" command

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

bash telnet session logging

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

Logging ALL standard out of a bash script to a log file, but still show on screen

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

running a bash script even after logging out from the current session

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

Command Logging

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 logging to file, limit lines

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
rdc(1M) 																   rdc(1M)

NAME
rdc - user interface for Routing Administration Manager (RAMD) SYNOPSIS
coresize] filesize] seconds] DESCRIPTION
provides a user-oriented interface for working with the and routing daemons. and are referred to as routing daemons. provides a command- line interface to start and stop these daemons. In addition, it provides commands to check the configuration file for syntax errors, make the daemon dump core, and dump the current state of the daemon. can reliably determine the running state of the routing protocols. This can be used in shell scripts to manipulate Options supports the following command-line options: Specifies that does not change the kernel forwarding table while running and routing daemons. This option is useful to test the daemons, when the daemons should operate as a route server that does not forward. Suppresses the stderr messages of and routing daemons. This option can be used to suppress informational messages that are normally printed to the standard output, and the log error messages through syslogd(1M). Specifies the time in seconds for which waits to start, stop, reconfigure and terminate daemons. By default, this value is set to 10 seconds. Specifies the maximum size of a core dump produced by the routing daemons invoked using Specifies the maximum size of a file produced or created by the routing daemons invoked using Commands The following commands are used to send HP-UX signals to or routing daemons for various purposes: Sends an abort signal to the requested daemon and terminates the daemon with a core dump. The core files are generated in the file where can be or Sends a signal to the requested daemon to dump its current state into the where is one of the routing daemons. Kills the daemon abruptly. This command is used when the daemon hangs. Sends signal to the requested daemon to reread its configuration file and reconfigure its current state. Sends signal to the requested daemon to terminate gracefully. Sends signal to the daemon to toggle the trace. If tracing is enabled, this command causes tracing to be suspended and the trace file to be closed. If tracing is disabled, the trace file is reopened and tracing initiated. This is useful to move the trace files. If or the routing daemon tracing is modified using this command and the daemons are reconfigured with the trace options, the effect on tracing is with respect to the configuration file. Sends signal to to recheck the interface configuration. periodically checks the kernel interface configuration for any changes. This command can be used to force the daemon to check the interface status immediately. Currently, the only valid argument for this com- mand is for checking on By default, obtains its configuration information from the file. maintains many versions of the configuration file. The versions of the configuration file maintained by are as follows: command of is used to create this configuration file. When must install a new configuration file using the command, the existing file is renamed as file. When creates a new configuration file, using the command, the existing file is renamed as and the existing is renamed as file. Configuration File Commands The following commands perform operations related to configuration files: Checks for syntax errors. This is done after changes are made to the configuration file and before reconfiguring the routing daemons. The system administrator use this command to ensure that there are no syntax errors in the configuration file, which can otherwise terminate the daemons on reconfiguration. Checks the file for syntax errors. Renames the file to retaining the older versions of the configuration files. This operation fails if does not exist. Replaces the old configuration file to This command fails, if the file does not exist or if the file is of zero length, or if the backout command deletes an existing, non-zero length file. Performs a operation even if the file exists and is of non-zero length. Sets all configuration files to mode 664, owner root and group trusted non-root user. This allows a trusted non-root user to modify the configuration files. Creates a new configuration file, with zero length. The file mode is set to 664, owner root and group trusted non-root user. This allows a trusted non-root user to install a new configuration file. Controlling Daemons The following commands can be used to control the daemons: Starts The command returns an error if is already running. It invokes and waits for the time period specified with option. A non-zero exit status is returned, if an error is detected while executing the binary, or if a lock is not obtained on the pid file within the speci- fied wait time. Starting invokes all the configured protocols in the configuration file of The following commands can be used to determine the current state of the daemon or to stop or restart and other IPv6 routing protocols. Determines if daemons are currently running. exits with a zero status if the daemon is running and with a non-zero value if the daemons are not running. Stops the requested routing daemon gracefully. Stopping stops all the daemons. Restarts the requested daemon. reports an error, if there is a failure. EXAMPLES
To start type the following at the HP-UX command prompt: If successful, the pid of the daemon is displayed. To get the current state of the daemons, type the following at command prompt: This will dump the current state of the and routing daemons. The dump files for the and routing daemons are and respectively; where is one of the routing daemons. To reconfigure the routing daemons, change the configuration file and issue the following command at the command prompt: AUTHOR
was developed by Future software Ltd. FILES
where, can be or the routing daemons. SEE ALSO
kill(1), ram_monitor(1M), ramd(1M), syslogd(1M), signal(2), ramd.conf(4). rdc(1M)
All times are GMT -4. The time now is 02:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy