Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
First, the service needs to be located in /etc/init.d/ in order to be properly managed.
Second, you should read the RUNLEVEL FILES section of the chkconfig man page.
Once you add the required chkconfig comments to your init script and it's located in /etc/init.d/ folder then the chkconfig --add sas.servers command will work (not ./sas.servers) and you can manage the service using chkconfig.
Other man pages you should look at on your redhat system include:
man chkconfig
man service
You're a Wizard, Harry! Yes that was my mistake, thank you for the suggestion and guidance sag47. Devilboy, I was trying to do what sag47 suggested. I appreciate both of yours time!
SAG47, I just saw in your profile that you have WIN X64 as well as are a linux expert. One question if I may please. Unrelated but I have been trying to communicate from a win64 7 pro to rhel 6 machine, hosts.deny and hosts.allow all commented out, sshd is running, but I keep getting connection refused, or when I run portQry form the windows side for a particular port (that port on rhel is listening (netstat -an|grep 8561) I get FILTERED status from PortQry. On WIN machine I turned off the firewall (for testing) also added PortQry in allow through firewall, no third party firewall running) but no resolution. MS tech support said it is RHEL that is refusing.
I will do the homework and reading but please if you could point me to where I should start looking, I am going nuts!
I run a mixed environment at home which is why you see Windows (for games).
It is likely being filtered by iptables (comes by default in RedHat) like devilboy suggested. What is the service you're trying to access over 8561? If it is ssh then check the service status for sshd running.
Code:
service sshd status
Also see if you're able to hook the service banner from ssh on the machine as well. From RedHat run,
Code:
telnet localhost 8561
If it returns with your ssh version and other minimal information then it is properly listening and likely the firewall (iptables).
The configuration file for iptables is located in /etc/sysconfig/iptables. You can find extensive documentation on iptables at netfilter.org. Here's possibly a good starting point for you to start researching. These rules were generated on a debian machine I administer (some modified) but it will give you a decent idea.
Code:
# Generated by iptables-save v1.4.4 on Wed Sep 28 08:51:40 2011
*filter
:INPUT ACCEPT [388:68427]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [196:19118]
-A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
#allow ssh over port 22
-A INPUT -p tcp -m tcp -m state --state NEW --dport 22 -j ACCEPT
#allow ping machine
-A INPUT -p icmp --icmp-type 8 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
#localhost gets everything
-A INPUT -s 127.0.0.1 -j ACCEPT
-A OUTPUT -s 127.0.0.1 -j ACCEPT
#End of rules, drop everything else
-A INPUT -j DROP
-A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7
COMMIT
# Completed on Wed Sep 28 08:51:40 2011
Keep in mind those rules may not work for you on your RedHat system but it gives you a general idea from which you could take. Also those rules allow the world on those ports. You should filter ip addresses by using the -s (source) option.
Thank you again, you folks are very kind people. Yes sir, I looked in enough google articles to look if sshd is running (it is). I came across someone's IP table rule, hate to admit went over my head. But I will start looking. RHEL and WIN are both inside my LAN. I do not access internet through them (that does not mean someone could not come in). It is a statistical application which is listerning on 8561 (installed on rhel machine). I was trying to have the web application server (jboss-GA) run on win7. That is where during install, it could not see the rhel machine (where app's metadata service runs).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.