On Junos OS Evolved platforms, alarmd error is generated upon config commit. For every commit, mgd(management daemon) sends SIGUSR1 signal to alarmd. When alarmd receives SIGUSR1, it does update the license infringement action.
On Junos OS Evolved platforms, alarmd error is generated upon config commit.
{master}[edit]
user@PTX10008-re0# run monitor start messages |match Alarm
user@PTX10008-re0# commit
re0:
configuration check succeeds
re1:
commit complete
*** messages ***
Mar 18 09:05:30.482 PTX10008-re1 mgd[16657]: UI_COMMIT_PROGRESS: Commit operation in progress: cannot signal 'Alarm control process', signal 10, no pid
Mar 18 09:05:31.099 PTX10008-re0 mgd[25516]: UI_COMMIT_PROGRESS: Commit operation in progress: cannot signal 'Alarm control process', signal 10, no pid
In EVO, license alarms are handled internally in license infra using alarmd object. Sending a signal to alarmd is not required in EVO, which is removed by PR1797233 .