Les Bell has taken more time to develope the preliminary System
Maintenance objectives. He has reviewed the task list for completion,
filling in gap in the current task list and implementing them into the
objectives. His files are attached.
Please review and comment as previously requested :)
Thank-you Les!
-Kara
---------- Forwarded message ----------
Date: Mon, 4 Jun 2001 12:45:34 -0500 (CDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Preliminary Kernel Objectives
In order to assist in speedy objective development, I've tried to start
developing some preliminary objectives for our tasks, based on the most
recent organizational structure. (I've only received one response to the
last thread on organizing!)
The objectives are definitely not complete in current form, nor are they
the concrete foundation we're forced to work with. The tasks are our
foundation (also attached). The goal is to create objectives which cover
these tasks and fill in the technical gaps and details.
Our Level 1 objectives
(http://www.lpi.org/http://www.lpi.org/p-obj-101.html and p-obj-102.html)
should provide a good outline for what form and style objectives should be
written in. I've modified slightly (including bullets for specified files
and tools covered) but the rest should be developed in the same fashion as
the current Level 1 objectives. There's no need to obsess over this step
at this stage, as I plan to have this completed in a stage of formal
review.
I would like either comments, changes, and additions as well as assistance
completing (technically) the objectives I've posted; your comments and
submissions for replacement or additional objectives; and your comments
for supplementary objectives (if any).
Please begin by reviewing the current objectives for Level 1 at the URLs
listed above. Next review the task file for this group. Finally, review
the preliminary objectives file and comment. Please note that the
preliminary objectives file associates the current task numbers with the
affiliated objective. Please continue to refer to these task IDs when
commenting, reorganizing, etc. objectives.
I will continue submitting preliminary objective files for various
categories today and tomorrow. I would like good discussion and progress
toward finalizing objectives in progress by Wednesday. By Friday, those of
you interested in the contract positions to finalize objectives should be
able to begin review. By next week, I would like to publish our objectives
for public review and begin collecting preliminary items.
The next 10 days are going to be crazy, and I greatly appreciate your time
and dedication to development. We are moving extremely quickly, and
everyone is very excited about our current developments!
Please contact me if you are available 6/8 - 6/12 for contract objective
review and development. I apologize that this will encompass a weekend,
but it is necessary for succeeding with our current development schedule.
Slots are filling for the Item Writing session planned for the week of
June 18. If you had hoped to participate in this event, please contact me
to discuss availability, expenses, etc. It is likely that a two team
approach (6/18 - 6/20, 6/20 - 6/22) will be used, allowing for flexible
travel arrangements.
--
Kara Pritchard Phone: 618-398-7360
Author, RHCE Exam Cram
Director of Exam Development http://www.lpi.org/
Site Manager http://www.LinuxUsersGroups.org/
--
System Maintenance Objectives
[3.16.2, 3.16.5, 5.1.11, 5.1.8, 6,1,6]
Objective: Configure logging
The candidate should be able to: Configure syslogd to act as a central
network log server. Configure syslogd to send log output to a central log
server. Log remote connections. Use grep and other text utils to automate
log analysis.
Includes tools and files such as:
* syslog.conf
[1.7.6]
Objective: Package software for distribution
The candidate should be able to: Build an RPM file. Rebuild an RPM file.
Includes tools and files such as:
* rpm
* .spec file format
[6.3.8]
Objective: Backup
The candidate should be able to: Create an offsite backup storage plan.
1.7.6 lo Build or rebuild an RPM file.
3.16.2 Set up a logging server
3.16.5 Change syslog's startup configuration to enable it to act as a central
network log server.
5.1.8 Log remote connections.
5.1.11 Redirect log output to a central log server by editing
/etc/syslog.conf.
6.1.1 L1 Check the /var/log/messages for any kernel messages
6.1.2 L1 Check the /var/log/secure for any bad or refused login
6.1.3 L1 Check the /var/log/xferlog for any user that should not done
transfers.
6.1.4 L1 Check the /var/log/maillog for null connections, bad auth logon for
relays, and rejects, any warnings.
6.1.5 L1 Check the /var/httpd/* look at all error logs. Look for bad requests.
Possible cracking stuff. If you are running a Linux box and see *.exe or *.dll in
requests logs.
6.1.6 L1 Check all /var/log for anything that is out of the normal by making a
file of normal log entries so you can grep -vf normal.log.
6.3.8 hi Create backup storage plan to prevent data loss in event of fire or
theft.
