Bash scripts do not normally cause anything to be logged anywhere. Perhaps you can describe the scenario and environment where this is happening in a bit more detail.
On a hunch, I'm guessing you might be talking about a cron job or similar which generates output which then gets sent to the administrator. In general terms, you can suppress regular output by redirecting it to /dev/null, like so:
If verbosecommand is correctly implemented, error messages will not be suppressed by this redirection (this is why we have separate "standard output" and "standard error"; the above discards only the "standard output").
Hi,
I am running a script where i need to run another command in a particular folder which I do not have access so I need
to login as su to that folder and run that script...what are the options I need so that I
can skip interactive mode ..here is what I tried..
#! /usr/bin/sh... (2 Replies)
Hi there
I get the following message im my messages file 2 or 3 times a second
Dec 4 11:44:18 my-box in.timed: connect from localhost
I would like to stop in.timed from logging to syslog altogether as this message is filling up my disk.
I dont want to stop daemon.info altogether... (0 Replies)
Hello
One of our applications initiates an ftp logon to itself twice every second ...(to check some files or something im not sure) but every time it does this it logs an entry into the wtmpx database, this file is now getting absolutely huge and whilst I know that I could implement some type of... (1 Reply)
Hi, I have googled for quite some time and couldn't able to get what exactly I am looking for.. My query is "how to stop a shell script which is running inside a remote server, using a script"??? can any one give some suggestions to sort this out. (1 Reply)
Hi All,
Sorry if it is a duplicate post. I have not got any reference about this anywhere.
I looked at the posts described in SSH - Passing Unix login passwords through shell scripts - Linux / UNIX Forum and it helped me till the point to connect to the host and executing the basic commands.... (3 Replies)
Hi everyone,
I have this problem with a script I'm writting. I want to execute a code running in the background several times through a script. I am writting it like that
parent_script
for a in 1 2 3 4 5
do
exec test -n $a
done
What I want to do is when parent_script is killed,... (0 Replies)
I am trying to write a script that can be called by other scripts to print output to a log. I also want to be able to rotate the log file for this script with a max of 5 logs files. This is what I have so far:
#/bin/ksh
. /taipso75/scripts/IPSM_run_profile.sh*
log=${IPSM_HOME}/log
(
echo... (1 Reply)
A Gbytes long log
/var/log/apache2/access_log
causes my question: How to stop my IP logging (just because of frequent AJAX/setTimeout).
As config:
SetEnvIf Remote_Addr "ip\.ip\.ip\.ip" dontlog
CustomLog /var/log/apache2/access_log common env=!dontlog
In
/etc/apache2/httpd.conf ... (0 Replies)
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
When I do "set -n" or "set -o noexec" the shell doesn't do what it sould.
Infact if I check:
$: set -o
....
noexec off
....
f
...instead I can set normally the other option.
Who Knows what could be up? (2 Replies)
Discussion started by: flaviofachin
2 Replies
LEARN ABOUT NETBSD
rsh
RSH(1) BSD General Commands Manual RSH(1)NAME
rsh -- remote shell
SYNOPSIS
rsh [-46dn] [-l username] [-p port] host [command]
rsh [-46dn] [-p port] username@host [command]
DESCRIPTION
rsh executes command on host.
rsh copies its standard input to the remote command, the standard output of the remote command to its standard output, and the standard error
of the remote command to its standard error. Interrupt, quit and terminate signals are propagated to the remote command; rsh normally termi-
nates when the remote command does. The options are as follows:
-4 Use IPv4 addresses only.
-6 Use IPv6 addresses only.
-d The -d option turns on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.
-l username By default, the remote username is the same as the local username. The -l option or the username@host format allow the remote
name to be specified.
-n The -n option redirects input from the special device /dev/null (see the BUGS section of this manual page).
-p port Uses the given port instead of the one assigned to the service ``shell''. May be given either as symbolic name or as number.
If no command is given, note that rlogin(1) is started, which may need a different daemon (rlogind(8) instead of rshd(8)) run-
ning on the server; you want to pass the rshd(8) port number in that case.
If no command is specified, you will be logged in on the remote host using rlogin(1).
Shell metacharacters which are not quoted are interpreted on local machine, while quoted metacharacters are interpreted on the remote
machine. For example, the command
rsh otherhost cat remotefile >> localfile
appends the remote file remotefile to the local file localfile, while
rsh otherhost cat remotefile ">>" other_remotefile
appends remotefile to other_remotefile.
FILES
/etc/hosts
SEE ALSO rcmd(1), rlogin(1), rcmd(3), hosts.equiv(5), rhosts(5), environ(7)HISTORY
The rsh command appeared in 4.2BSD.
BUGS
If you are using csh(1) and put a rsh in the background without redirecting its input away from the terminal, it will block even if no reads
are posted by the remote command. If no input is desired you should redirect the input of rsh to /dev/null using the -n option.
You cannot run an interactive command (like rogue(6) or vi(1)) using rsh; use rlogin(1) instead.
Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here.
BSD March 9, 2005 BSD