[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Thu Jan 15 16:58:04 2004 -->
- <!--x-from-r13: psbjyre ng bhgcbfgfragvary.pbz (Quevf Tbjyre) -->
- <!--x-message-id: 1074203664.4516.6.camel@devel -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Setting up a Centralized Syslog server. -->
- <li><em>date</em>: Thu Jan 15 16:58:04 2004</li>
- <li><em>from</em>: cfowler at outpostsentinel.com (Chris Fowler)</li>
- <li><em>in-reply-to</em>: <<a href="msg00589.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00589.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] Setting up a Centralized Syslog server.</li>
The directory structure would look like this:
syslog/192.168.0.1/<facility>
On Thu, 2004-01-15 at 16:51, John Cole wrote:
> Howdy all!
>
> Currently I have just one device that is spitting out Syslog files. I'm
> currently trying to setup a centralized syslog server that will handle
> firewall, vpn, windows event logs from servers, etc.
>
> I know that I can setup the firewall/vpn do point to local0-local7. I want
> to have each incoming log dumped to a different file. There are about 10
> servers that I want to do this on. Does anyone have any pointers on how to
> make this work?
>
> Also, I'm at a crossroads between going with RH and SuSe. Any
> ideas/comments on both for making something like this work?
>
> Thanks,
> John Cole, TICSA
>
> Network Administrator / Security
> Lockheed Georgia Employees' Federal Credit Union
> 430 Commerce Park Drive
> Marietta, GA 30060
> (770) 424-0060
> (800) 541-8921
> Disclaimer: The information contained in this email is proprietary and
> confidential. It is intended solely for the use of the person identified
> and intended as the recipient. This document is forwarded to you in such a
> form (E-mail) that LGEFCU cannot guarantee the completeness and/or
> correctness of its contents and information. If you have received this
> E-mail message in error, please notify us immediately. Please also delete
> this document from your computer. This document may not be reproduced,
> copied, distributed, published, modified, or furnished to third parties,
> without the prior written consent of LGEFCU. LGEFCU specifically disclaims
> any responsibility or liability for any personal information or opinions of
> the author expressed in this email.
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00593" href="msg00593.html">[ale] Setting up a Centralized Syslog server.</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Chris Fowler)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00589" href="msg00589.html">[ale] Setting up a Centralized Syslog server.</a></strong>
<ul><li><em>From:</em> JohnC at LGEFCU.org (John Cole)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00590.html">[ale] ALE NW meeting tonight?</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00592.html">[ale] Setting up a Centralized Syslog server.</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00589.html">[ale] Setting up a Centralized Syslog server.</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00593.html">[ale] Setting up a Centralized Syslog server.</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00591"><strong>Date</strong></a></li>
<li><a href="threads.html#00591"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>