Depending how many you are poking, you might consider these adjustments too:-
The blue -q is to suppress some of the normal output to keep your log file a little clearer, however the log file will probably still collect anything that is displaed by the server login process e.g. from /etc/profile or ~/.bashrc
I've added the green to speed up the timeout if the server does not respond. You might want to adjust it depending on what your network will allow.
The red hostname is a command to run on the server you are connecting to. You have $HOSTNAME which may be undefined or set to anything in the shell's environment prior to this script.
What output do you actually want? Is it a list of hosts you could not connect to? If you can open the IP connection, but if fails to sign in how would you handle that? You script would probably just hang. Other conditions may cause your script to carry on to the next host immediately, e.g. the server's public key is different and you get an alert about a possible man-in-the-middle attack. The ssh exits with a non-zero return code, but you don't check. Perhaps you just want a list of successes to then target those that don't let you connect. Knowing the goal would be useful for us.
Hi. I have a kornshell script that runs on a daily basis as a cron job. Part of what the script does is copy the folder contents from another server to the current server (server where KSH script is running).
I have a scp command, as follows:
scp $REMOTE_HOST:$REMOTE_FILE_DIR/* $TMP_DIR
... (8 Replies)
Hi,
I am new to Shell Scripting. Can anybody help me in writing a Script Which Could Login from a Unix box to a Remote Unix box which accepts the user credentials automatically and display the result for checking the Disk Space Utilisation (Without running any SSH agent). (1 Reply)
Hi all,
I'm writing a script that chooses the best computer available in an open lab. The script works great except every now and then there is a dead computer in the lab that begins the ssh handshaking, but freezes after the following:
debug1: Offering public key:
When the script happens... (2 Replies)
Hello there.
I'm fairly new to Linux, but I am connecting via SSH and PuTTY to a remote server, and I am running a fairly heavy MySQL script in a PHP page.
Our connection here is dodgy to say the least and I get continuous disconnections.
My question is, when I get disconnected, does my... (4 Replies)
Hi all,
Im new at scripting and i need to run a few commands at work every hours so i decide to make a script but on 1 of the steps i have a the follwoing problem:
The command i do is this:
#!/bin/bash
ssh root@asdasd001 'mysql -h A-db-1 -uroot -password --execute "show slave status"'... (3 Replies)
Hello;
I regularly run monitoring scripts over ssh to monitoring scripts
But whenever a server is hung or in maintenance mode, my script hangs..
Are there anyways to trap exit status and be on my way ??
Looked at the ssh manpage and all I can see is a "-q" option for quiet mode ..
Thank... (2 Replies)
Hey,
I need a script that tries to connect via SSH to a remote server
and that remote server might not be up yet, so retry until succeed
the error message I get if the server is not up yet is:
ssh: connect to host 127.0.0.1 port 40001: Connection refused
any idea of a good way to do it ?
... (5 Replies)
Dear Folks,
I am trying to read a config file contains ip and port numbers.
i want to read each line of the config file and check ssh connection is happening or not.
Kindly guide.
Config file:
abc@1.2.342 22
abc@1.2.343 22
abc@1.2.344 22
abc@1.2.345 22... (9 Replies)
Hello guys!
I am setting up a script to access a unix remote server. My problem is that when I put the ssh line "my host", the script does not wait for the server response asking for the password to execute the line in which I put the password, that is, I need to put a form in which script has a... (1 Reply)
Discussion started by: aroucasp
1 Replies
LEARN ABOUT DEBIAN
colorgccrc
COLORGCCRC(5) File Formats Manual COLORGCCRC(5)NAME
colorgccrc - configuration file for colorgcc
DESCRIPTION
A colorgccrc configuration file is used to configure the highlighting of the compiler output from colorgcc.
SYNTAX
Each line consists of a keyword designating a configuration variable. The keyword is followed by `:' and then one or several values
(depending on the keyword). Lines beginning with a hash mark `#' are comments.
CONFIGURATION VARIABLES
g++ | gcc | c++ | cc | g77 | gcj | gnat | gpc
Specifies the paths to the compilers. Takes one value; a path to the compiler.
nocolor
Specifies what terminal types colorization should be disabled on. Takes one or several values, separated by whitespace.
srcColor
Specifies the highlighting attributes source-code should be given. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
introColor
Specifies the highlighting attributes for normal compiler output. Takes one or several color attributes. See the section COLOR
ATTRIBUTES for more information.
warningFileNameColor | errorFileNameColor
Specifies the highlighting attributes for the filename in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningNumberColor | errorNumberColor
Specifies the highlighting attributes for the line-number in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
warningMessageColor | errorMessageColor
Specifies the highlighting attributes for the message-text in a warning or an error, respectively. Takes one or several color
attributes. See the section COLOR ATTRIBUTES for more information.
COLOR ATTRIBUTES
The following attributes are valid for highlighting.
clear, reset
bold, underline, underscore, blink, reverse, concealed
black, red, green, yellow, blue, magenta, cyan, white
on_black, on_red, on_green, on_yellow, on_blue, on_magenta, on_cyan, on_white
SEE ALSO gcc(1), colorgcc(1)HISTORY
Jan 15 2003: Initial version of this manual-page.
REPORTING BUGS
Report bugs to <jmoyers@geeks.com>
AUTHORS
Jamie Moyers <jmoyers@geeks.com> is the author of colorgcc.
This manual page was written by Joe Wreschnig <piman@sacredchao.net>, and modified by David Weinehall <tao@debian.org>, for the Debian
GNU/Linux system (but may be used by others).
COPYRIGHT
Copyright (C) 2003 Jamie Moyers
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Jan 15, 2003 COLORGCCRC(5)