I presume you are doing this as root. You allow root to ssh onto all your servers ?
Using rudiC example. Just add & on the end and/or </dev/null
If you are running remote ssh commands on a list of servers, you have to add
</dev/null at the end or it will exit after the first one.
With just </dev/null it will run the command on each server in foreground one after another.
You can also add & to the end and it will execute the command in background on each server and return at once.
Test the script with the echo first and then remove, when you want to use it.
Last edited by Scrutinizer; 04-17-2015 at 01:49 AM..
Reason: CODE tags
I need a shell script for OS X, one that can find IP addresses of machines connected to my LAN, get the names of the computer associated with those addresses, then display them like so in a list: "Bob's L33T Boxx: #.#.#.#" Something like the network scanner in Apple Remote Desktop is what I'm... (1 Reply)
Hi
I have a mix of solaris 8,9 & 10. I need to have our 6 Solaris servers shutdown buy a script that will be executed by APC network Shutdown software
Im really not sure how I would write a script to shut them down and the following processes?
the processes are
portmapper
seq
seq_api... (1 Reply)
i really dont know any other way to put it besides that Ubuntu 8.04, that i just installed on my computer hangs when it shuts down. the bar depletes the orange like it should, but it never actually shuts down.
anyone know whats going on? (3 Replies)
Hello all.
I have built a cluster of 9 Macs for computational chemistry and I need a shell script that I can use from one computer to all the rest to shutdown.
I have modified all of the Macs so that there is pass-wordless ssh. As well, I have modified each "visudo" file on each machine by... (1 Reply)
on solaris 8 i edited file rc0 in /sbin at last line
ex.
/sbin/sync; /sbin/sync; /sbin/sync
# Unmount file systems. /usr, /var, /var/adm, /var/run are not unmounted by
# umountall because they are mounted by rcS (for single user mode) rather than
# mountall. If this is changed,... (1 Reply)
#!/bin/bash
for ((n=0 ; n < 254 ; n+=1))
do
ip=192.168.0.$n
if ping -c 1 -w 1 $ip > /dev/null 2> /dev/null >> /etc/logping.txt; then
echo "${ip} is up" # output up
# sintax >> /etc/logping.txt log with .txt format
else
echo "${ip} is down" # output... (4 Replies)
I just installed this 11.2 ver and when I tell it to shutdown it takes for ever then just hangs with this just a little bit of that red line left to go, then it just sits there like forever until I get tired of looking at it then force a shutdown by holding my power button down until my laptop... (8 Replies)
Discussion started by: userx-bw
8 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)