| |
N1URO > PACKET 12.02.20 09:32l 39 Lines 1510 Bytes #999 (0) @ WW
BID : 40504_N1URO
Read: GUEST
Subj: Re: PE1RRR > * from systemd
Path: IZ3LSV<I3XTY<I0OJJ<I0OJJ<GB7CIP<N1URO
Sent: 200212/0208Z @:N1URO.#CCT.CT.USA.NOAM #:40504 [Unionville] $:40504_N1URO
>From n1uro%n1uro.#cct.ct.usa.noam@i0ojj.ampr.org Wed Feb 12 03:10:42 2020
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0m.1) with SMTP
id AA99262 ; Wed, 12 Feb 2020 03:10:42 +0100
Message-Id: <40504_N1URO@i0ojj.bbs>
>From: n1uro@n1uro.#cct.ct.usa.noam
X-JNOS-User-Port: Telnet (i0ojj @ 44.134.32.240) -> Sending message
From: N1URO@N1URO.#CCT.CT.USA.NOAM
To : PACKET@WW
Red et al
That's a *lot* of work to use systemd to do what in a sense is load a bash
script! Here's some tricks for you (and perhaps others)...
- Use Devuan linux. They've basically refused to incorporate systemd. SysVinit
is still the primary loader which works cleaner (imho) for starting services
via bash scripting. They will support systemd but the main system loader is
still sysvinit.
The rest of your how to you should be able to do the following to your main
loader script that might be a lot easier for starting your binary as the user
you wish to load it as. For the loader script you can do:
chown <user>.<group> <script>
then chmod +x <script>
and chmod u+s <script>
If that doesn't load the binary you wish as the user you wish to load it as
you can try this:
chown <user>.<group> <binary>
chmod u+s <binary>
This trick is supposed to execute the script and binary as the user you
specify with chown. If you're calling a script and/or binary under
sudo -u <user> and a password isn't required this could be a bit dangerous
from a security perspective.
73 de N1URO
---
SendBBS v1.1 by N1URO for LinFBB
Read previous mail | Read next mail
| |
