Nathaniel van Diepen
Nathaniel van Diepen
`launcherctl status` would be another output you could share to show what launcher you are on. Forgot to ask for that instead. What you provided works though. Everything looks fine...
I haven't tested this as there is no easy way in the current repo, and I don't have capacity to set up a standalone test repo for it right now....
It's probably worth pulling this into a different package that `toltec-base` depends on, since it should be a `rmall` package.
> what's the motivation for this? Allow a user to easily manage entware services with systemd since we don't use the entware init stuff. This avoids spinning up their init...
I noticed a reference to `/opt/etc/init.d/rc.unslung start` in one of the generic entware install scripts. Perhaps we should use this instead?
Upon reviewing the systemd.generator documentation, it looks like generators will not work, as it runs too early in the boot process. Having a systemd service that runs after `opt.mount` to...
A template unit is what I settled on. Upon reviewing `rc.unslung`, it didn't really make sense to run another init system underneath systemd. From what I understand, it's shipped with...
What does `systemctl status rmfakecloud-proxy` output?
The device token is unrelated to if the proxy is able to run or not. The issue you have right now is that the proxy isn't running, so the device...
> Got it. Here's the output. > > ``` > invalid upstream address: parse "192.168.3.100:8000": first path segment in URL cannot contain colon > ``` Oh, you should set your...