first see my earlier comment https://github.com/dmwm/deployment/pull/115#r10074583.

start action must update the DB, otherwise, at least we shall modify the sysboot() command to call ```start_das_with_update```. And the operators would have to call ```manage start_das_with_update``` instead of ```manage start``` when starting the service after installation. I'm not sure if we want this.

another issue is stop() action, if start_das_with_update is called within another action (as a bash function), it is hard to identify that it is running (and in which stage) and thus just killing DAS service might not stop DAS service, as it would start only after the update is finished. this is why so far it's calling a separate sub-process.
**another and probably the best solution would be storing a pidfile for a running DAS process, and using it for killing. this way we'd ensure only one instance running and obtain easy and relieable killing**