Submit a Story      Security   FAQ    Resources    Certification    Links    Calendar    Forum    Polls    Search      
User Functions
:

:

Don't have an account yet? Sign up as a New User
Lost your password?

What's New
STORIES
No new stories

COMMENTS last 2 days
No new comments

TRACKBACKS last 2 days
  • GroupWise 2012 no...

  • LINKS last 2 weeks
    No recent new links


    Who's Online
    Guest Users: 9

    Live Novell Chat
    Live Novell Chat

    Topics
    Home
    Poll posts (1/0)
    Way Off Topic! (1/0)
    Contracting (2/0)
    FAQ (1/0)
    NetWare (51/0)
    Certification (31/0)
    NDS/eDir (19/0)
    Administration (78/0)
    GroupWise (143/0)
    Linux/Open Source (309/0)
    Resources (21/0)
    General News (904/0)
    Security (291/0)

    Poll
    How do you think the Attachmate deal will turn out for "Novell"
    Well, the marketing can't be any WORSE
    Better, the product/support commitment is there
    Worse, MS will end up with what is left of Novell’s marketshare & still end up with the patents, leaving the customer as the loser
    Results
    86 votes | 0 comments

    Poll
    Does your company still use Blackberry phones?
    Yes, with BES
    Yes, without BES
    No, we never used Blackberries
    No, we just stopped using them
    No, we stopped using them 6 months ago
    No, we stopped using them 1+ year ago
    Results
    55 votes | 0 comments

    Novell Advisor
    There was a problem reading this feed (see error.log for details).


     Fourth Commandment of Systems Administration    
     Author:  ph0bia
     Dated:  Tuesday, May 17 2005 @ 01:55 PM CDT
     Viewed:  1,850 times  
    AdministrationIn a followup to The Commandments of Systems Administration Newsforge has posted the latest installment; The Fourth Commandment of Systems Administration: Thou Shalt Keep Server Logs on Everything.

    The role of system administrator is a role of details. Heavily used and updated servers are filled with details, from new tables in a database to root password changes. These details need to be documented. When you are managing three servers, these details can be easy enough to remember. However, when you have 30 or 50 or 100 servers, the details become impossible to keep track of without documenting them. When it matters, you don't want to think that the IP address of that old accounting server is 192.168.10.55, you want to know it.

    All I can say about this is that: at a minimum have a central syslogd server on your network, and throw syslog (or syslog-ng)at it from everything that can throw syslog at it. Routers, switches, servers, services, print server boxes, everything. Lock that syslogd box down and run alerting tools against those logs, such as Epylog, or log2mail - configure those tools to alert you when root login failures and the like happen. Rotate those logs to keep them managable (logrotate or similar. Keep those logs forever, burn them to disc.



    What's Related

    Story Options
  • Mail Story to a Friend
  • Printable Story Format

  • Trackback

    Trackback URL for this entry: http://www.abend.org/trackback.php/20050517135536989

    No trackback comments for this entry.
    Fourth Commandment of Systems Administration | 2 comments | Create New Account
    The following comments are owned by whomever posted them. This site is not responsible for what they say.
    Fifth Commandment of Systems Administration
    Authored by: ph0bia on Monday, May 23 2005 @ 08:59 PM CDT
    The Fifth Commandment of Systems Administration: Policies & Documentation is now up on Newsforge.
    scrawl
    Authored by: Anonymous on Saturday, August 19 2006 @ 01:11 PM CDT