No promises other than that I'll try.
@endomain So, here's the .service file for my message bus. It works and is responsive: https://github.com/virtadpt/exocortex-halo/blob/master/exocortex_xmpp_bridge/xmpp_bridge.service
Here are the ones that didn't come up, possibly because they gave up before the message bus finished starting:
I know I'm doing something wrong in here, but after a couple of attempts I'm not sure what.
I think the pattern is After= and Requires=, not After= and Wants= ?
Wants= is a very soft statement compared to requires:
A weaker version of Requires=. Units listed in this option will be started if the configuring unit is. However, if the listed units fail to start or cannot be added to the transaction, this has no impact on the validity of the transaction as a whole. This is the recommended way to hook start-up of one unit to the start-up of another unit.
Also, I just recalled this. The simple service type doesn't understand that your service has a startup time.
You can force a wait in your [Service] section for dependent units to cheaply work around this for now:
@endomain Hmmm... I can't necessarily predict how long it'll take for the message bus to come online due to my home link.
I just scanned through my code and didn't find any "bot can't reach message queue so it dies" code.
Is there a service type that does have a concept of a startup time?
A bunch of technomancers in the fediverse. Keep it fairly clean please. This arcology is for all who wash up upon it's digital shore.