Rustmilian

joined 2 years ago
[โ€“] [email protected] 2 points 9 months ago* (last edited 9 months ago)

I don't disagree with you whatsoever...
I'd however like to also mention that people like "veganteacher" need to stop equating feeding your child some steak to rape...

[โ€“] [email protected] 19 points 9 months ago (1 children)

Hits all the hallmarks of a shitpost. ๐Ÿ‘Œ

[โ€“] [email protected] 7 points 9 months ago

Butter with the dog on em.

 
[โ€“] [email protected] 3 points 9 months ago

Good to hear that it worked.
To explain env, typically when systemd is running a service it only provides a very minimal environment. When using env it passes more of the environment variables and whatnot from userspace, so it's likely that the binary daemon was looking for specific environment variables and it returned an empty string and that's what caused error, it's also useful if the daemon's location changes during runtime or if it's not in a standard location.

[โ€“] [email protected] 3 points 9 months ago* (last edited 9 months ago) (2 children)

Try ExecStart=/usr/bin/env /path/to/daemon
Also what's the output of ldd /path/to/daemon & sudo systemd-run /path/to/daemon ? Maybe check systemctl show-environment. Maybe try adding Type=simple , this tells systemd that the service will fork.

If that fails, we could try ExecStart=/usr/bin/strace -f -o /tmp/daemon_strace.log /path/to/daemon for stactrace & ExecStart=/bin/sh -c '/path/to/daemon > /tmp/daemon.log 2>&1' to log the daemon.

[โ€“] [email protected] 3 points 9 months ago* (last edited 9 months ago) (4 children)

Is the daemon a binary? If so drop the bash part and try sudo chmod 755 /path/to/daemon.

[โ€“] [email protected] 1 points 9 months ago* (last edited 9 months ago) (6 children)

I assume so, but just to be sure, have you run sudo systemctl enable blah.service then reboot? It'll symbolic link to the systemd auto start service and run it at boot.
Also, make sure everything is marked as executable; especially whatever you have "/path/to/daemon" set as. sudo chmod +x /path/to/daemon
Restart the service or reboot then :
sudo systemctl status blah.service

[โ€“] [email protected] 1 points 9 months ago* (last edited 9 months ago) (8 children)

What's the specific VPN service? I'll check their docs.

[โ€“] [email protected] 4 points 9 months ago* (last edited 9 months ago) (10 children)

On that, make sure it's in the root systemd path. Something like /etc/systemd/system/blah.service, placing it in the user systemd service path (~/.config/systemd/user/) will cause permission errors as it'll try accessing the root user from the current user.

[โ€“] [email protected] 2 points 9 months ago

Just burn your worn clothes and buy new ones; the true fashion industry experience.

89
... (lemmy.world)
 
46
submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]
 
202
submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]
 

~Non-Commercial Use Only~

317
Hole-In-One (lemmy.world)
 
 
241
submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]
 
view more: next โ€บ