Linux System Administration Recipes A Problem-Solution Approach

CHAPTER 12 ■ MANAGING TIME AND PEOPLERequire valid-user# We don't use kerberos auth for the "noauth" areas of RT - these are the# areas that run outgoing mail and other similar things.Order allow,denyAllow from allSatisfy anyOrder allow,denyAllow from allSatisfy anyNext, you need to edit RT_SiteConfig.pm to add these lines:Set($WebExternalAuto , 1);Set($WebExternalAuth , 1);Reload Apache2 (/etc/init.d/apache2 force-reload) to implement the changes, and then trylogging on with your Kerberos password.■ Note The $WebExternalAuto line also sets RT up such that if a new user logs in or sends a request by e-mail,a user account is automatically added. This saves you time!12-6. Getting Big Projects DoneAs discussed in recipe 12-1, sysadmin work by its nature tends to be interrupt-driven. As well assometimes making it hard to keep track of, this can also mean that it’s hard (or seems hard) to find timeto sit down and work on larger projects, such as replacing servers, introducing new pieces of software,or doing web site revamps if that’s part of your job (as it may be in a smaller company), and so on.There are a couple of solutions to this. Probably the first thing to do is to make sure that only theprojects that really need to be large undertakings are in fact time-consuming. Server replacement, forexample, such as when acquiring a new desktop machine, should be straightforward and automated asfar as possible. (Of course, setting up the automation itself may come under the heading of a largeproject!).In general, make sure that you’re being as time-efficient as possible. The general rule is that by thesecond time you do something, you should be looking at automating it. Some issues may come up onlyonce; it’s rare for something to come up only twice. It’s much more likely that it’ll return again, at whichpoint any time taken in automating it becomes valuable.You should seek to minimize the amount of effort it takes just to keep things running smoothly. Bycentralizing your systems (see Chapters 2 and 3), keeping good notes and records (see Chapter 1), andkeeping your systems secure (see Chapter 6), you should aim to have as much as possible of your setup243Download at WoweBook.Com