For the time being, you may want to comment out any and all Arch Linux
and Manjaro related stuff in installinit.sh until proper systemd
scripts are created for them.
After reporting to you that the search for Manjaro also needed to be
done in installinit.sh, I realized there are no init scripts to be installed, and since both Manjaro and Arch Linux are systemd based now
(as well as others, I'm sure), the current state of both in MBSE are
not going to install proper startup scripts.
installinit.sh includes:
cp init.Arch $DISTINIT
but there is no init.Arch in the script directory, so this will not
work. Just as well, I'm not even sure Arch Linux supports sysvinit any more unless you go out of your way to make it do so.
So at the moment, you could probably just comment out (or remove) the complete "# Adding scripts for Arch Linux" section in installinit.sh,
and everything should still work as expected. Both Arch Linux and
Manjaro will still be labeled and installed properly, just without any kind of startup script or service file installed at the moment.
I began working on a little something, but need more time. Until then,
the above should be okay - and on both Arch Linux and Manjaro mbtask
will need to be run manually by the MBSE admin user. When I get
something working as far as systemd goes, I'll let you know.
I need to setup a machine with Arch Linux so I can figure out what is needed in the systemd way of doing things.
I began working on a little something, but need more time. Until
then, the above should be okay - and on both Arch Linux and
Manjaro mbtask will need to be run manually by the MBSE admin
user. When I get something working as far as systemd goes, I'll
let you know.
Keep in touch here or via netmail.
It's not that big a deal. Just a simple .service file is usually
required, although the one I started yesterday failed possibly due to
the fact that the MBSE admin user needs to start it, and not root
(which I think is default for systemd service files). So I'll just
have to look into starting it as a user or even passing it off to the
user once it's started.
It's not that big a deal. Just a simple .service file is usually
required, although the one I started yesterday failed possibly
due to the fact that the MBSE admin user needs to start it, and
not root (which I think is default for systemd service files). So
I'll just have to look into starting it as a user or even passing
it off to the user once it's started.
You can specify the user and group in the .service file:
User=, Group=
Sets the Unix user or group that the processes are executed as, respectively. Takes a single user or group name or ID as argument. If
no group is set, the default group of the user is chosen.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,018 |
Nodes: | 17 (0 / 17) |
Uptime: | 36:32:31 |
Calls: | 503,137 |
Files: | 228,109 |
D/L today: |
17,533 files (3,463M bytes) |
Messages: | 440,140 |