Customizing a Notification daemon error log

By default, the Notification daemon error log starts when the Notification server starts. Use this procedure to customize the InfoPrint Notification daemon error log.
  1. Find the notifyd_error.cfg file from the /usr/lpp/pd/bin directory where the file is installed and copy it into the /var/pd directory: 
    cp /usr/lpp/pd/bin/notifyd_error.cfg /var/pd/notifyd_error.cfg
    Note: If you already customize your Notification daemon error log, remember to change the name or move the current notifyd_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 notifyd_error.cfg file that you created and specify the settings for the log attributes that you want.
    For example, you can modify the log-backup-number attribute, which lets you specify the number of backup logs that InfoPrint saves, including the initial error.log.BAK file.

    Sample notifyd_error.cfg file provided by InfoPrint Manager

    #
#  Error Log Configuration File
#
log-size = 1024
log-wrap = true
log-severity = debug
log-backup-number = 10

    When you start the Notification daemon 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 default, the log-backup-number attribute specifies a value of 10, meaning that you can have nine back up files with timestamps and the initial .BAK file. You can reduce this number as low as 1 or increase it as high as 999.

    For a complete list of the error log attributes that you can customize, see the see the "Attributes for logs" section in "InfoPrint object attributes" chapter of RICOH InfoPrint Manager: Reference.

  3. Once you have finished defining your options, save and close the /var/pd/notifyd_error.cfg file.
    Note: If you do not need the customization change to take effect immediately, you can skip the final two steps and just wait until the next time the Linux system where the InfoPrint Manager server is installed on is restarted.
  4. From an Linux command line, specify stopnotd to shut down the Notification daemon so that these customization changes can take effect.
  5. Enter startnotd to restart the Notification daemon.
Parent topic: Customizing error logs in the InfoPrint Manager server