Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 327

Customizing error logs in the InfoPrint Manager AIX server

Page 327 highlights

Chapter 32. Customizing error logs in the InfoPrint Manager AIX server InfoPrint Manager provides three configuration files for various InfoPrint Managers servers and daemons: 1. spl_error.cfg for the InfoPrint Manager server error log. 2. notifyd_error.cfg for the Notification daemon error log. 3. sap_error.cfg for all the SAP daemons. If you want to customize error logs for one of these servers or daemons to control their size, whether they wrap, the severity level of messages written to the logs, and the number of back-up logs that InfoPrint Manager saves, do one of the following procedures. Customizing an InfoPrint Manager server error log By default, the InfoPrint Manager server error log starts when the InfoPrint Manager server starts. Use the following procedure to customize the InfoPrint Manager server error log(s). Any InfoPrint Manager server processes that are running on this AIX server are changed by this customization the next time they are started. 1. Find the spl_error.cfg file in the /usr/lpp/pd/bin directory and copy it into the /var/pd or %PDBASE% directory: cp /usr/lpp/pd/bin/spl_error.cfg /var/pd/spl_error.cfg Note: If you already customize your server error logs, remember to change the name or move the current spl_error.cfg file in /var/pd so that your customization values can be copied over into the newer version of the file. 2. Open the copy of the spl_error.cfg file that you created and specify the settings for the log attributes that you want (as shown in Figure 32). For example, you can modify the log-backup-number attribute, which allows you to specify the number of backup logs that InfoPrint saves, including the initial error.log.BAK file. # # ErrorLog Configuration File # # Log size (units = KBytes) log-size = 1024 # Wrap On? log-wrap = true # Severity? log-severity = debug # Number of backup log files log-backup-number = 10 Figure 32. Sample spl_error.cfg file provided by InfoPrint Manager When you start the InfoPrint Manager server after a shut down, it backs up the first error log by creating an error.log.BAK file. With each successive restart, it creates an additional .BAK file, adding a timestamp as a fourth qualifier. By © Copyright InfoPrint Solutions Company 1998, 2010 313

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418

Chapter 32. Customizing error logs in the InfoPrint Manager
AIX server
InfoPrint Manager provides three configuration files for various InfoPrint
Managers servers and daemons:
1.
spl_error.cfg
for the InfoPrint Manager server error log.
2.
notifyd_error.cfg
for the Notification daemon error log.
3.
sap_error.cfg
for all the SAP daemons.
If you want to customize error logs for one of these servers or daemons to control
their size, whether they wrap, the severity level of messages written to the logs,
and the number of back-up logs that InfoPrint Manager saves, do one of the
following procedures.
Customizing an InfoPrint Manager server error log
By default, the InfoPrint Manager server error log starts when the InfoPrint
Manager server starts. Use the following procedure to customize the InfoPrint
Manager server error log(s). Any InfoPrint Manager server processes that are
running on this AIX server are changed by this customization the next time they
are started.
1.
Find the
spl_error.cfg
file in the
/usr/lpp/pd/bin
directory and copy it into the
/var/pd
or
%PDBASE%
directory:
cp /usr/lpp/pd/bin/spl_error.cfg /var/pd/spl_error.cfg
Note:
If you already customize your server error logs, remember to change the
name or move the current
spl_error.cfg
file in
/var/pd
so that your
customization values can be copied over into the newer version of the file.
2.
Open the copy of the
spl_error.cfg
file that you created and specify the settings
for the log attributes that you want (as shown in Figure 32).
For example, you can modify the
log-backup-number
attribute, which allows
you to specify the number of backup logs that InfoPrint saves, including the
initial
error.log.BAK
file.
When you start the InfoPrint Manager server after a shut down, it backs up the
first error log by creating an
error.log.BAK
file. With each successive restart, it
creates an additional
.BAK
file, adding a timestamp as a fourth qualifier. By
#
# ErrorLog Configuration File
#
# Log size (units = KBytes)
log-size = 1024
# Wrap On?
log-wrap = true
# Severity?
log-severity = debug
# Number of backup log files
log-backup-number = 10
Figure 32. Sample spl_error.cfg file provided by InfoPrint Manager
© Copyright InfoPrint Solutions Company 1998, 2010
313