Bash - here document on RHEL 6.8 and 6.9 servers aren't working
H Forum,
I was thankful in getting help from this post that allowed me to connect to multiple severs at once using here documents to gather data into variables. But I've discovered that the same bash command that works on my RHEL 7 servers do not work on RHEL 6? What's strange about my problem is that I'm not getting an error either. The problem is that the variables return empty when I try the following code on RHEL 6.8 or 6.9 servers we manage:
I've thought of adding in the ability to determine if my server is RHEL 6 or 7 using code like the following:
python -mplatform | grep -qi red &&
but even if I could determine RHEL version I'm still not sure why my RHEL 6 servers do not return variable data back. I've tested this above code connecting to just one server to try and triage the issue. No errors are returned. the variable fields are just empty. Whereas on my RHEL 7 servers I return back variables with no issue. Could it be that how I use Here Documents just doesn't work with RHEL 6 servers? has anyone seen this before?
I've also tested connecting to a RHEL 6 server multiple times to get the data I need. what I mean by this is instead of connecting to a RHEL 6 server once and collecting data I've tested connecting to a RHEL 6 for each command I need so connecting multiple times and there are no issues with the above commands I'm issuing.
Perhaps I'll just need to identify RHEL 6 servers and gather their data differently than I do for RHEL 7 severs but before I do that I thought I would check this forum for any advice first.
I tried doing
ftp myhost <<HERE
username
password
quit
HERE
but it doesnt work. Why?
When I do ftp host, I always get prompted for username, and once I type that in I get prompted for password. But when I try doing it from here document it freezes. (2 Replies)
Hello all,
I am planning to deploy a configuration / auditing software package for about 100 new nodes that we are planning to install. I am hearing many good things in regards to cfengine and puppet. Can someone shed some light in regards to these solutions?
Thanks,
jaysunn (1 Reply)
Have a sudo statement inside of a here document. It prompts me for a password, but doesnt wait for me to enter my password. Is there a way I can use the command without sudo or anyway that I can enter the password correctly?
Eg :
while read remotehost
do
ssh -t $2@$remotehost <<REMOTE... (13 Replies)
Hello Unix Mates
I have a problem my script is not working, can anyone tell what is rung with it?
#!/bin/sh
wget "http://download.divx.com/labs/divx611-20060201-gcc4.0.1.tar.gz"
tar zxf divx611-20060201-gcc4.0.1.tar.gz
./divx611-20060201-gcc4.0.1/install.shError:
-2010-11-28 21:25:06-- ... (1 Reply)
I am being pushed from AIX onto RHEL 6 and after our first 'chuck it on' install, I have a problem. Where is the old (okay insecure) telnet & ftp server? I know that they are probably regarded as archaic now, but the source servers do not have the SSH tools, so I've got to somehow transfer the... (4 Replies)
I was testing Networking Teaming (activebackup) with a VM hosted on VmWare Workstation and VirtualBox, and the result is, if the active interface is down, the system is not using the backup interface.
Tested on both CentOS / RHEL 7
Please find below the command I have used to configure teaming.... (0 Replies)
RHEL 7.1 client using autofs to mount a NIS map of home directories being exported by a Solaris 10x86 nfs server.
The owner and group are correct on the NFS server, but on the RHEL client, the owner and group end up being nobody nobody. The USERS and GROUPS are NIS maps as well. They are... (2 Replies)
Hi,
I need help on syslog-ng on RHEL 7.2. It is working as expected.
As per configuration, it is supposed to create authlog, messages and xymessages daily in respective folder of date. But I can see only messages file and that is also not updating well.
# ps -ef | grep -i syslog
root 22954... (1 Reply)
Discussion started by: solaris_1977
1 Replies
LEARN ABOUT CENTOS
ksc
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)