SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Though it does not answer your question, can't you simply make rc.firewall executable (chmod +x rc.firewall) and place it in /etc/rc.d to get it to start (per /etc/rc.d/rc.inet2)?
Also, I would think that you want your firewall started before going online. I thought /etc/rc.d/rc.local was the las thing to start, so this would insure that you had a firewall before going online. I could be messed up on the order, though. Just read through the scripts in /etc/rc.d to make sure.
Originally posted by shilo Though it does not answer your question, can't you simply make rc.firewall executable (chmod +x rc.firewall) and place it in /etc/rc.d to get it to start (per /etc/rc.d/rc.inet2)?
Also, I would think that you want your firewall started before going online. I thought /etc/rc.d/rc.local was the las thing to start, so this would insure that you had a firewall before going online. I could be messed up on the order, though. Just read through the scripts in /etc/rc.d to make sure.
not that i run a software firewall.. but wouldnt the network need to be started before the firewall could be started?
Originally posted by carboncopy Okay,
I have created individual rc scripts for each action..
Question:
What is the . infront of the execution line bout, example from rc.K
Code:
if [ -x /etc/rc.d/rc.samba ] ; then
. /etc/rc.d/rc.samba stop
fi
The period is equivalent to the source command.
The files in /etc/rc.d are read in by the shell as opposed to being executed as programs.
Same results but there is a difference in the effect on the shell enviroment between the two techniques.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.