Advertisement

09.03.2008 at 10:34AM PDT, ID: 23700099
[x]
Attachment Details

How to set up a syslog server

[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.7
Tags:

Fedora, Core, 5, Syslog

Hello Experts,
I have a Netscreen SSG Firewall and IronMail S10D appliance on my network, and would like to set up a syslog server for them to send logging info to.  I currently have a Fedora Core 5 box built and available for this purpose.  If a more recent version would work better, or a different distribution, I can work with that as well.  What I would like to accomplish is to have the two appliances send syslog info to the syslog server, with the logs going into seperate directories, and I would also like to rotate the logs on a daily basis.  I observed a similar process performed by a co-worker a number of years ago, but do not remember much about it.  To this point, I have added the -r option to the /etc/sysconfig/syslog file, and have created two directories (/netscreen and /ironmail) in the /var/log directory as the targets for the logs from the two sources.  I have also added a rule to the firewall of the Fedora box allowing incoming traffic on UDP port 514.  However, when I attempt to direct syslog traffic from my firewall to the Fedora box, it is unable to connect.  If memory serves, I will need to make configuration changes using two facilities (presumably Local0 and Local1)?  If anyone can point me in the direction of a good, thorough tutorial on this, or offer suggestions, I would greatly appreciate it!!  I am pretty new to Linux and working my way through it the best I can, so the more detail the better...
Thanks very much,
Russ Dillion
 
Expert Comment by cjl7:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
Author Comment by rdillion:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
Expert Comment by raatti:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
Author Comment by rdillion:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
Accepted Solution by raatti:

All comments and solutions are available to Premium Service Members only. Start your 7-day free trial to view the solution to this question.

Already a member? Login to view this solution.

 
 
20081119-EE-VQP-46 / EE_QW_2_20070628