Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 12 ■ MANAGING TIME AND PEOPLERightsA fundamental aspect of RT that you need to understand is the rights system. This governs who can dowhat operations to and with tickets. Here are some example rights (operations that can be undertakenon or with tickets):• CreateTicket: Create a ticket in a queue.• ModifyTicket: Change a ticket.• SeeQueue: Be able to see the queue at all.• OwnTicket: Have a ticket allocated to you to fix.• ShowTicketComments: See the comments on a ticket.• TakeTicket: Allocate a ticket to yourself.• ShowScrips: Look at the scrips that apply to a ticket. See the “Scrips” section formore about this.■ Note The full list is available by selecting Queues Select Queue Group/User Rights.Particularly important is that if a user doesn’t have ShowTicket rights, then even if they have createda particular ticket, they won’t be able to see it. Similarly, without SeeQueue rights, they cannot see thequeues (and thus see other tickets).In a basic setup, the most straightforward option is to start by giving all rights to the AdminCcgroup. This will mean that anyone watching the queue via this group (as per the previous setup) willhave full queue admin rights. Highlight all the rights next to the AdminCc group (under the Group Rightsmenu item), and click Save Changes.After this, you can decide which rights to give to all users. CreateTicket, ModifyTicket,ReplyToTicket, SeeQueue, ShowOutgoingEmail, and ShowTicket make up a good basic set, becausethese are most of the tasks users will want to do. They’ll be able to create tickets (this one is prettyessential!) and modify or reply to their own ticket (and as discussed earlier, ShowTicket is required forthem to see their own ticket). They’ll also be able to see other tickets in the queue. ShowOutgoingEmailmeans that they’ll be able to see an e-mail that has been attached to their ticket. You can experiment andsee what suits your setup best. Some environments might prefer not to have other tickets visible to allusers, for example.238Download at WoweBook.Com
CHAPTER 12 ■ MANAGING TIME AND PEOPLE■ Note It is probably a good idea to distinguish between ShowTicket and ShowTicketComments. This enablesyour admin team to make comments that cannot be seen by users. A comment is a way of adding a note to aticket. In the default setting, a comment will be forwarded only to people watching the ticket, not to the originator.In contrast, you can also reply to a ticket, which will add a note to the ticket and also e-mail both the originatorand anyone watching the ticket.However, it is not a good idea to use this distinction between replies and comments as a reason to be rude behindthe back of the ticket originator! It does mean that you can keep technical information in the comments to avoidconfusing nontechnical users or add references to other tickets that are related to the back end of your system(and uninteresting to nonsysadmin users).User rights work in a similar way and are administered via Configuration Groups Select Group Group Rights (to change the rights for all group members) or User Rights (to set rights for groupmembers individually). You can also set various global rights via Configuration Global User Rights.Rights that can be given to users include SuperUser rights.ScripsThe final important part of RT is scrips. These are scripts (specifically, chunks of Perl) that run undercertain conditions. It is the part of the system that enables one of the benefits of RT: that it can update allinterested parties by e-mail.There are a collection of default scrips that apply to all queues; you can find them underConfiguration Global Scrips or from the Scrips menu item of individual queues). Looking at thedefault setup, you will see that these distinguish between Correspond and Comment. On Correspond,there are three scrips. These send e-mails to AdminCcs, Requestor, Ccs, and Other Recipients, whenevera Correspond event happens (that is, when someone replies to the ticket). On Comment, there are onlytwo scrips, one to e-mail AdminCcs and one to e-mail Other Recipients. This is because the default setupdoes not e-mail comments to the ticket requestor. You can modify or delete these scrips by clickingthem. For example, you can alter the template used or alter the action. There are a collection ofpredefined actions, as shown in Figure 12-1.239Download at WoweBook.Com
Page 2:
Download at WoweBook.Com
Page 5 and 6:
Download at WoweBook.Comiii
Page 7 and 8:
Contents■About the Author .......
Page 9 and 10:
■ CONTENTS3-7. Writing a Nagios P
Page 11 and 12:
■ CONTENTS■Chapter 8: Using the
Page 13 and 14:
■ CONTENTSAbout the Author■Juli
Page 15 and 16:
■ CONTENTSAcknowledgmentsMany tha
Page 17 and 18:
■ CONTENTSIntroductionThis book i
Page 19 and 20:
■ INTRODUCTIONDownloading the Cod
Page 21 and 22:
C H A P T E R 1■ ■ ■Saving Yo
Page 23 and 24:
CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44:
CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86:
CHAPTER 3 ■ MONITORING AND UPDATI
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
C H A P T E R 4■ ■ ■Taking Ba
Page 117 and 118:
CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
C H A P T E R 5■ ■ ■Working w
Page 141 and 142:
CHAPTER 5 ■ WORKING WITH FILESYST
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
C H A P T E R 6■ ■ ■Securing
Page 157 and 158:
CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
CHAPTER 7 ■ WORKING WITH APACHEOn
Page 181 and 182:
CHAPTER 7 ■ WORKING WITH APACHEdi
Page 183 and 184:
CHAPTER 7 ■ WORKING WITH APACHE4.
Page 185 and 186:
CHAPTER 7 ■ WORKING WITH APACHE
Page 187 and 188:
CHAPTER 7 ■ WORKING WITH APACHEAl
Page 189 and 190:
CHAPTER 7 ■ WORKING WITH APACHE
Page 191 and 192:
C H A P T E R 8■ ■ ■Making Be
Page 193 and 194:
CHAPTER 8 ■ USING THE COMMAND LIN
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208: CHAPTER 9 ■ WORKING WITH TEXT IN
Page 223 and 224: C H A P T E R 10■ ■ ■Things G
Page 225 and 226: CHAPTER 10 ■ THINGS GO IN, THINGS
Page 233 and 234: C H A P T E R 11■ ■ ■Tracking
Page 235 and 236: CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 237 and 238: CHAPTER 11 ■ TRACKING DOWN BUGS01
Page 239 and 240: CHAPTER 11 ■ TRACKING DOWN BUGS
Page 245 and 246: CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 247 and 248: CHAPTER 11 ■ TRACKING DOWN BUGSAn
Page 249 and 250: CHAPTER 11 ■ TRACKING DOWN BUGS#
Page 251 and 252: C H A P T E R 12■ ■ ■Managing
Page 253 and 254: CHAPTER 12 ■ MANAGING TIME AND PE
Page 257: CHAPTER 12 ■ MANAGING TIME AND PE
Page 267 and 268: APPENDIX■ ■ ■Perl TipsSee rec
Page 269 and 270: APPENDIX ■ PERL TIPS• Date::Par
Page 271 and 272: APPENDIX ■ PERL TIPSPerl Syntax N
Page 273 and 274: ■ ■ ■Index■Symbols$CDPATH,
Page 275 and 276: ■ INDEXenscript option (printing)
Page 277 and 278: ■ INDEX■NNagiosadding hosts to,
Page 279 and 280: ■ INDEXsyslogcentralized logging
Page 281 and 282: Download at WoweBook.Com
show all

Linux System Administration Recipes A Problem-Solution Approach

Create successful ePaper yourself

Delete template?

Save as template?