Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 121

How do you manage the contents of the PSF DSS accounting data file?, podaccount.log

Page 121 highlights

ainurpt1 Reports accounting data stored in accounting.log, sorted by actual destination. ainurpt2 Reports accounting data stored in accounting.log, sorted by job submitter. ainurpt3 Reports times and pages printed by the job submitter from accounting.log. ainurpt4 Reports audit data stored in audit.log, sorted by actual destination. ainurpt5 Reports audit data stored in audit.log, sorted by job submitter. ainurpt6 Reports times and pages printed by the job submitter from audit.log. ainurpt7 Reports post-printing accounting data stored in jobcompletion.log, sorted by actual destination. ainurpt8 Reports summary post-printing accounting data stored in jobcompletion.log, sorted by job submitter. ainurpt9 Reports detailed entries of times and pages printed for a specific job submitter in jobcompletion.log. For examples using these utilities, see InfoPrint Manager: Reference or the man pages for the utilities. How do you manage the contents of the PSF DSS accounting data file? An installation with a regular schedule of printing jobs will accumulate accounting and audit data that must be managed carefully to avoid potential performance problems. Periodically, the log files must be either purged or moved to a different directory. If you do not do either of these tasks, your installation will run out of space on the file system, preventing you from printing any more jobs. To avoid this problem, you should purge or move the accounting and audit logs as part of your system maintenance. To retain a record of PSF DSS accounting and audit data, you need to move the existing log files to a new directory. Use this procedure: 1. Go to the directory where the log file, for example, podaccount.log, is located by specifying: cd /var/psf 2. Move the podaccount.log file to a directory named 1quarter96 by specifying: mv podaccount.log /1quarter96 This command moves the existing file to the new directory and removes it from the /var/psf directory. The next time a job is submitted for printing from InfoPrint Submit, InfoPrint will create a new podaccount.log file in the /var/psf directory and write a single line of data for each job. We recommend you move the data to another file system rather than deleting it from the system. This lets you store accounting data and delete it from the system Chapter 8. Gathering accounting and auditing data about print jobs 107

  • 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

ainurpt1
Reports accounting data stored in
accounting.log
, sorted by actual
destination.
ainurpt2
Reports accounting data stored in
accounting.log
, sorted by job submitter.
ainurpt3
Reports times and pages printed by the job submitter from
accounting.log
.
ainurpt4
Reports audit data stored in
audit.log
, sorted by actual destination.
ainurpt5
Reports audit data stored in
audit.log
, sorted by job submitter.
ainurpt6
Reports times and pages printed by the job submitter from
audit.log
.
ainurpt7
Reports post-printing accounting data stored in
jobcompletion.log
, sorted
by actual destination.
ainurpt8
Reports summary post-printing accounting data stored in
jobcompletion.log
, sorted by job submitter.
ainurpt9
Reports detailed entries of times and pages printed for a specific job
submitter in
jobcompletion.log
.
For examples using these utilities, see
InfoPrint Manager: Reference
or the man pages
for the utilities.
How do you manage the contents of the PSF DSS accounting
data file?
An installation with a regular schedule of printing jobs will accumulate accounting
and audit data that must be managed carefully to avoid potential performance
problems. Periodically, the log files must be either purged or moved to a different
directory. If you do not do either of these tasks, your installation will run out of
space on the file system, preventing you from printing any more jobs. To avoid this
problem, you should purge or move the accounting and audit logs as part of your
system maintenance.
To retain a record of PSF DSS accounting and audit data, you need to move the
existing log files to a new directory. Use this procedure:
1.
Go to the directory where the log file, for example,
podaccount.log
, is located
by specifying:
cd /var/psf
2.
Move the
podaccount.log
file to a directory named
1quarter96
by specifying:
mv podaccount.log /1quarter96
This command moves the existing file to the new directory and removes it from
the
/var/psf
directory. The next time a job is submitted for printing from
InfoPrint Submit, InfoPrint will create a new
podaccount.log
file in the
/var/psf
directory and write a single line of data for each job.
We recommend you move the data to another file system rather than deleting it
from the system. This lets you store accounting data and delete it from the system
Chapter 8. Gathering accounting and auditing data about print jobs
107