I am not sure if we are the first the first one to notice this, but, we have recently came across a strange issue. where "smpolicysrv status" command causing siteminder policy server to restart.
We usually use "smpolsrv -status" to check the status of the policy server as follows:
$ smpolsrv -status
SiteMinder Policy Server is running
One of my teammate had a typo in the command and issued "smpolicysrv status" instead of "smpolsrv -status".
which restarted the policy server and created new smps log file with smps.<date>.<time>.log format(example: smps_20170203_132830.log)
Ideally if "status" is not a valid option with "smpolicysrv" utility, it should give appropriate error, instead of restarting the policy server.
This issue is reproducible on all policy server in our environment.
ProductName=CA SiteMinder Policy Server
Any insight on this will be highly appreciated!