Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
I hope this is not a stupid question, I am still early in the learning stage. I am looking for advice on how to replicate files on a daily basis from SYSTEM A (Fedora core 2) to SYSTEM B (Red Hat 9). They are both on the same subnet and behind a firewall so security is not a high priority. I am just needing an easy, automated way to update some files on SYSTEM B with files from SYSTEM A daily. Thanks for any help anyone can provide.
I think this is going to do the trick but I am running into another problem. We use a non standard port for SSH. When I use /usr/bin/rsync -e ssh -pXXXX -avzp /path/* server:/path/ I get the messege that rsync: -pXXXX: unknown option. How can I tell rsync that it needs to use a port other then port 22 when it sync's up?
O.k. it works when I run it manually and can type the password in, but how to I get it to use the password when running from a cron? Again-- security is not a high priority-- both systems are on the same subnet and behind a firewall.