03-02-2010
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I need a KSH script that will check a host file for duplicate IP's and/or host names and report out the errors. Anyone out there have one they would like to share?
Something like:
Hostname blahblah appears X times
IP Address xxx.xxx.xxx.xxx appears X times
TIA (4 Replies)
Discussion started by: ThreeDot
4 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
Can anyone tell/guide me how to check remote host is up/running using bash script?
Thanks.
Zulfiqar (5 Replies)
Discussion started by: zulfikarmd
5 Replies
3. Shell Programming and Scripting
I am using KSH and I need to check whether the remote host has been configured with ssh public key. Is there any way we can check inside a script? (6 Replies)
Discussion started by: praveenbvarrier
6 Replies
4. Shell Programming and Scripting
Hi,
My script needs to check whether the remote host is up or not.
If it is up i need to start few servers in that host or else just a notification should be sent that the remote host is down?
Could someone help me out in this?
Regards
Arun (4 Replies)
Discussion started by: arunkumarmc
4 Replies
5. Red Hat
Hi,
I'm interesting do you have a some solution/good practice how upgrade/update OS with possibility to back previously release (something like Live upgrade in Solaris) ?
thanks. (2 Replies)
Discussion started by: deivo
2 Replies
6. Shell Programming and Scripting
Hey all,
I have a script that I use for some automated installs. Unfortunately for the script to work the server that it's running from needs to have host-key authentication setup to the target server. If it isn't setup beforehand and the script is executed the install partially completes and... (1 Reply)
Discussion started by: Rike255
1 Replies
7. UNIX for Dummies Questions & Answers
I am able to connect to a remote host using the legacy IP and port 2222.
Today the remote has a new IP I am unable to connect.
How to check if the remote host is blocking or if its my server is unable to connect.
Err Msg : telnet: Unable to connect to remote host: Connection refused
Err... (5 Replies)
Discussion started by: ITDev01
5 Replies
8. SCO
Hello,
I have an old system SCO 5.0.2 HOST (without network) and some applications on this machine. Theses applications are not installable again on other system because i have not the routines. And it's now necessary to connect this old system on local network for a "new" application.
I have SCO... (13 Replies)
Discussion started by: Lm76
13 Replies
9. Solaris
Hi all,
1) how do i check which FS(filesystems) in the current active PBE are shared and not shared with the ABE (alternate boot env) ?
is doing lufslist and comparing between the 2 BEs the only option ?
2) when doing a luactivate -s (synchronize), does the synchronization go both way... (0 Replies)
Discussion started by: javanoob
0 Replies
10. UNIX for Beginners Questions & Answers
Hi all, posting my first time, hope not breaking posting rules with it, if yes, let me know.
I'm trying to build a script to check a file in an sftp server through a remote server.
The intention is to check the file in a sftp host, and if the file is found or not, it should send an email.... (4 Replies)
Discussion started by: MrShinyPants
4 Replies
KSC(1) User Commands KSC(1)
NAME
ksc - Linux kernel module source checker
SYNOPSIS
ksc [ -d | --directory ] DIRECTORY
ksc [ -k | --ko ] FILE
OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify
options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it
checks for the specific architecture for which the binary was built.
Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4
-h, --help
show this help message and exit
-c CONFIG, --config=CONFIG
path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from
/etc/ksc.conf
-d DIRECTORY, --directory=DIRECTORY
path to the directory
-i, --internal
to create text files to be used internally.
-k KO, --ko=KO
path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the
same time then only -d is used and the -k option is discarded.
-n RELEASENAME, --name=RELEASENAME
Red Hat release against which the bug is to be filed. Default value is 6.5
-p PREVIOUS, --previous=PREVIOUS
path to the previous resultset file and submit it as a bug to Red Hat Bugzilla.
-r RELEASE, --release=RELEASE
RHEL whitelist release used for comparison
-s, --submit
Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The
tool will prompt for bugzilla password.
The configuration file looks like below:
[bugzilla]
user=user@redhat.com
partner=partner-name
partnergroup=partner-group
server=https://bugzilla.redhat.com/xmlrpc.cgi
-v, --version
Prints KSC version number
ksc - Version 0.9.11 Feb 2014 KSC(1)