# Is it sane to override launch.service if INITSYSTEM=on?

**URL:** <https://forums.balena.io/t/is-it-sane-to-override-launch-service-if-initsystem-on/1785>\
**Category:** Product support\
**Tags:** systemd\
**Created:** [August 31, 2017, 1:42am UTC](https://forums.balena.io/t/is-it-sane-to-override-launch-service-if-initsystem-on/1785 "2017-08-31T01:42:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bgentry](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/bgentry/32/419_2.png) [@bgentry](https://forums.balena.io/u/bgentry)\
**Post date:** [August 31, 2017, 4:45pm UTC](https://forums.balena.io/t/is-it-sane-to-override-launch-service-if-initsystem-on/1785/3 "2017-08-31T16:45:01Z")

</div>

Hi @floion,

Is the Dockerfile actually relevant here? I meant this as a general question as to whether it’s considered a good or bad practice to override `launch.service` (the systemd unit that launches the user application, such as [this one](https://github.com/resin-io-library/base-images/blob/master/debian/launch.service)).

I’ve read in other forum posts that with `INITSYSTEM=on`, the container no longer gets restarted when the application crashes, and that this is expected behavior ([here](https://forums.balena.io/t/raspberry-pi-resets-every-40-seconds-if-offline/1556/15), for example). And in that specific post, @imrehg recommends overriding the application launch service, which I guess answers my question on whether it’s acceptable to do that.

In either case, it might be worth documenting all this stuff in the `INITSYSTEM` documentation: [https://docs.resin.io/runtime/runtime/#init-system](https://docs.resin.io/runtime/runtime/#init-system)

---

_[View the full topic](https://forums.balena.io/t/is-it-sane-to-override-launch-service-if-initsystem-on/1785)._