Sponsored Content
Top Forums Shell Programming and Scripting How to run same script on multiples servers Post 302336237 by s_linux on Tuesday 21st of July 2009 03:40:30 PM
Old 07-21-2009
Thanks for your reply.
I forgot to mention that, I get an email after I run the scripts, so if I set up ssh to run the scripts on multiple servers, can I put results from all servers to one file,then send an email instead of sending mail from each server. Thanks
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ksh to run servers

I want to write a Kshell program which will start the servers(Oracle,DataIntegrator). Can anybody help me with this? I would appreciate your help. Thanks in advance (0 Replies)
Discussion started by: pari111222
0 Replies

2. AIX

is it ok to run AIX mksysb script on vio servers?

Hi to all now we running mksysb to nim on aix servers. we are planning to take mksysb from vio servers. can we use the same script for vio servers. thanks (10 Replies)
Discussion started by: honeym210
10 Replies

3. UNIX for Advanced & Expert Users

Command to run across servers

Hi, I have to run several unix commands like lsof or sed and need to execute across different servers as part of my monitoring tasks. There are around 40 Unix Servers. It is really cumbersome to run those command on several servers. can some help me in this regard. Is it possible to run... (6 Replies)
Discussion started by: john_prince
6 Replies

4. Shell Programming and Scripting

Need a script to run on multiple mail servers..

Hello, I am a Unix newbie and I need a script in which I can run a command on multiple servers at work. The command is to start a storage process and I am sick of doing it manually on all servers.. Here's the command: /opt/bss/bin/snmptable -CB -v2c -c P67LzuBm hostname hrStorageTable... (4 Replies)
Discussion started by: kinyyy
4 Replies

5. Shell Programming and Scripting

run vi/vim encrypted shell script without decryption on multiple servers

Hello Everyone, How do we run vi/vim encrypted shell script without decryption on multiple servers. It is a simple bash script and vim -nx <filename> has been used to encrypt with desired password. Now I have few errors, the syntax is absolutely fine as I have run that script multiple times on... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies

6. Shell Programming and Scripting

Run a script in parts on 2 servers

Hi all, I have a task for which I need to run some commands on one server1 and then jump from the server1 (using ssh and asking user to enter login credentials manually for server2 server) to server2 and run some commands there and exit. I know the script I need here but problem is when I... (5 Replies)
Discussion started by: pat_pramod
5 Replies

7. Shell Programming and Scripting

Run multiples jobs in background mod

Hi, I have a problem runnig from script two diferents process in background mod. Is there a limitation to do this? For example echo "Running process one:" ./ProcessOne & echo "Running process two:" ./ProcessTwo & echo "The process are runnig. Bye" The problem is that the... (7 Replies)
Discussion started by: Xedrox
7 Replies

8. AIX

How to write a script to run without password on a batch of servers?

I need run a command such as ps -ef |grep xxx on a batch of servers, how to write a script to run it without password? don't need go in each server to check? Thanks (7 Replies)
Discussion started by: rainbow_bean
7 Replies

9. Shell Programming and Scripting

Run a script on multiple servers

I need to run a script on a bunch of remote servers. how can this be done without ssh into each individual server and run it its under /sbin/script.sh on each server (1 Reply)
Discussion started by: tdubb123
1 Replies

10. Shell Programming and Scripting

Run a shell script on all 15 servers at the same time?

We have 15 servers. Hostnames for these 15 servers are stored in a text files and loop through each server to connect to the remote server and run a command, but this loop process runs the command one after another. However, the requirement is to run the same command on all 15 servers at the same... (10 Replies)
Discussion started by: laknar
10 Replies
proxsmtpd(8)						    BSD System Manager's Manual 					      proxsmtpd(8)

NAME
proxsmtpd -- an SMTP server for performing filtering SYNOPSIS
proxsmtpd [-d level] [-f configfile] [-p pidfile] proxsmtpd -v DESCRIPTION
proxsmtpd is an SMTP filter that allows you to perform arbitrary filtering on email. It accepts SMTP connections and forwards the SMTP com- mands and responses to another SMTP server. The DATA email body is intercepted and scanned before forwarding. Email can be altered, bounced, or silently dropped. proxsmtpd aims to be lightweight and simple rather than have a myriad of options. The options it does have are configured by editing the proxsmtpd.conf(5) file. See the man page for proxsmtpd.conf(5) for more info on the default location of the configuration file. OPTIONS
The options are as follows. -d Don't detach from the console and run as a daemon. In addition the level argument specifies what level of error messages to dis- play. 0 being the least, 4 the most. -f configfile specifies an alternate location for the proxsmtpd configuration file. See proxsmtpd.conf(5) for more details on where the configuration file is located by default. -p pidfile specifies a location for the a process id file to be written to. This file contains the process id of proxsmtpd and can be used to stop the daemon. -v Prints the proxsmtp version number and exits. FILTER SCRIPTS
The filter script is specified using the FilterCommand option. By default the email is piped through the script on standard input. Standard output is read for the filtered email. Standard error is also read for error messages. If the FilterType option is set to 'file', your filter will operate on a file rather than processing standard in and standard out. The file name will be passed to your filter command using the EMAIL environment variable. Your script can change the file as needed. Standard error is still processed as outlined below. If the filter command returns a successful exit code (ie: 0), then the filtered email is sent to the destination mail server as usual. When a error exit code (ie: anything but 0) a failure message is sent back to the sending server. In this case the email is not sent. You can customize the error message sent back. The last line of output printed to standard error will be used in this case. If you specify a full SMTP error code then it will be used (ie: '550 Bad Email'). If it's just a text message then a 550 SMTP error code will be used. You can silently drop messages by using an error message with a 250 SMTP code. This gives the illusion to the sending server that the email was accepted. Various environment variables will be present when your script is run. You may need to escape them properly before use in your favorite scripting language. Failure to do this could lead to a REMOTE COMPROMISE of your machine. CLIENT The network address of the SMTP client connected. EMAIL When the FilterType option is set to 'file', this specifies the file that the email was saved to. RECIPIENTS The email addresses of the email recipients. These are specified one per line, in standard address format. REMOTE If proxsmtpd is being used to filter email between SMTP servers, then this is the IP address of the original client. In order for this information to be present (a) the SMTP client (sending server) must an send an XFORWARD command and (b) the SMTP server (receiving server) must accept that XFORWARD command without error. REMOTE_HELO If proxsmtpd is being used to filter email between SMTP servers, then this is the HELO/EHLO banner of the original client. In order for this information to be present (a) the SMTP client (sending server) must an send an XFORWARD command and (b) the SMTP server (receiving server) must accept that XFORWARD command without error. SENDER The email address for the sender of the email. SERVER The network address of the SMTP server we're connected to. TMPDIR The path to the temp directory in use. This is the same as the TempDirectory option. LOGGING
proxsmtpd logs to syslogd by default under the 'mail' facility. You can also output logs to the console using the -d option. LOOPBACK FEATURE
In some cases it's advantageous to consolidate the filtering for several mail servers on one machine. proxsmtpd allows this by providing a loopback feature to connect back to the IP that an SMTP connection comes in from. To use this feature specify only a port number (no IP address) for the OutAddress setting in the configuration file. This will cause proxsmtpd to pass the email back to the said port on the incoming IP address. Make sure the MaxConnections setting is set high enough to handle the mail from all the servers without refusing connections. TRANSPARENT PROXY FEATURE
A transparent proxy is a configuration on a gateway that routes certain types of traffic through a proxy server without any changes on the client computers. proxsmtpd has support for transparent proxying of SMTP traffic by enabling the TransparentProxy setting. This type of set- up usually involves firewall rules which redirect traffic to proxsmtpd and the setup varies from OS to OS. The SMTP traffic will be forwarded to it's original destination after being scanned. Note that some features (such as SSL/TLS) will not be available when going through the transparent proxy. Make sure that the MaxConnections setting is set high enough for your transparent proxying. Because proxsmtpd is not being used as a filter inside a queue, which usually throttles the amount of email going through, this setting may need to be higher than usual. SECURITY
There's no reason to run this daemon as root. It is meant as a filter and should listen on a high TCP port. Care should be taken with the directory that proxsmtpd writes its temporary files to. In order to be secure, it should not be a world write- able location. Specify the directory using the TempDirectory setting. Make sure you understand the issues involved with escaping external data. The environment variables such as SENDER or RECIPIENTS need to be treated with care. If running proxsmtpd on a publicly accessible IP address or without a firewall please be sure to understand all the possible security issues. This is especially true if the loopback feature is used (see above). SEE ALSO
proxsmtpd.conf(5) AUTHOR
Stef Walter <stef@memberwebs.com> proxsmtp June 1, 2019 proxsmtp
All times are GMT -4. The time now is 09:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy