This article applies to BoKS Manager 6.7.0, 6.7.1 and 7.0.0.


In rare cases BoKS could kill unrelated (non-BoKS) processes.

Resolution / Workaround

To resolve this issue, apply the hotfix HFBM-0123 (for BoKS Manager 6.7 / 6.7.1) or hotfix HFBM-0124 (for BoKS Manager 7.0), available for download from the HelpSystems Community Portal.

The hotfixes address two problems:

  1. If an entry was left in btmp after the user had logged out (for example if the user logged in with BoKS active and logged out with BoKS inactive), it was not removed by boks_bksd on all platforms (it was removed on AIX and Solaris). If the process id (pid) was reused later by an unrelated process, boks_bksd would attempt to kill it. This has been fixed so the btmp entry is removed by boks_bksd within 30 seconds after the corresponding process is gone making it highly unlikely that another process has been assigned that pid in the meantime.
  2. Some BoKS daemons did not remove their pid files in $BOKS_var/run when they exited. Normally the BoKS Boot script would then try to kill the process with that pid before removing the file. If the process pid had been reused in the meantime the Boot script would then kill the unrelated process. This was much less likely than scenario 1) as normally there would only be a small time window for this to happen.
    Two things have been done to fix this:
    a) All daemons except httpsrv and pwm will now remove their pid file on normal exit.
    b) Code has been added to the Boot script to map pid file name to the name of the corresponding BoKS daemon. Before attempting to kill a process with a pid file left, the Boot script will now check using the ps command that the pid actually is for that BoKS daemon. If not, it will not kill it, only remove the file.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018