'ProcessGuard', 'ProcessMonitor' and 'ProcessCleaner' names

[elBoberido]

Somehow it felt like ProcessGuard, ProcessMonitor and ProcessCleaner do not fit together and I think I finally know why.

ProcessGuard

• quite abstract but some kind of a guard for the process
• alternatives could be AliveGuard or ProcessAliveGuard
• it tells what it does (more or less)

ProcessMonitor

• it tells what it can be used for but not what it does
• it actually only tells whether the ProcessGuard is active or not, only on a higher level we infer that the process is alive or not
• how about calling this ProcessGuardMonitor to tell what it does

ProcessCleaner

• again, it tell what it can be used for but not what it does
• it actually only tells whether the ProcessGuard should be cleaned up and also does it on drop
• how about calling it ProcessGuardCleaner to tell what it does

I'm not sure whether ProcessGuard is too broad but I think the two other constructs should just append Monitor and Cleaner to whatever the first one will be called.

[elBoberido]

The task of the ProcessGuard is similar to that of the canary in mining. Therefore, it could become Canary, CanaryMonitor and CanaryCleaner/CanaryDisposer?