From: thetredev <thetredev@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Add a service for iscsid (open-iscsi)
Date: Wed, 30 Nov 2022 20:30:56 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40861@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
New issue by thetredev on void-packages repository
https://github.com/void-linux/void-packages/issues/40861
Description:
When the `open-iscsi` package is installed on Arch Linux, a systemd service is created which essentially calls `/usr/bin/iscsid -f` when started:
```shell
$ cat /etc/systemd/system/multi-user.target.wants/iscsid.service
[Unit]
Description=Open-iSCSI
Documentation=man:iscsid(8) man:iscsiuio(8) man:iscsiadm(8)
DefaultDependencies=no
After=network-online.target iscsiuio.service iscsi-init.service
Before=remote-fs-pre.target
Wants=remote-fs-pre.target
Requires=iscsi-init.service
[Service]
Type=notify
NotifyAccess=main
ExecStart=/usr/bin/iscsid -f <-----
KillMode=mixed
Restart=on-failure
[Install]
WantedBy=multi-user.target
Also=iscsid.socket
```
I wanted to run Void as a server for testing purposes and I need `iscsid` to run on there. I've created the following service file as a first:
```shell
$ cat /etc/sv/iscsid/run
#!/bin/sh
[ -r conf ] && . ./conf
exec iscsid -f
$ sv status /var/service/iscsid
run: /var/service/iscsid: (pid 825) 311s
```
`iscsiuio` doesn't start for me for some reason, but `iscsid` is happy as far as I can tell. I'm quite sure that `iscsi-init.service` is NOT needed, since that only creates a `/etc/iscsi/initiatorname.iscsi` file which the XBPS package installation already does AFAIK.
My question/request: Do we need that service? If so, is my `/etc/sv/iscsid/run` enough? :)
Thank you!
next reply other threads:[~2022-11-30 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 19:30 thetredev [this message]
2022-12-01 13:21 ` open-iscsi: Add a runit service (iscsid) kruceter
2022-12-01 13:23 ` kruceter
2022-12-02 10:46 ` ahesford
2022-12-02 11:25 ` thetredev
2023-03-03 2:20 ` github-actions
2023-03-03 20:42 ` thetredev
2023-03-12 16:52 ` leahneukirchen
2023-03-19 13:23 ` thetredev
2023-03-19 15:23 ` leahneukirchen
2023-03-19 16:37 ` thetredev
2023-06-18 2:07 ` github-actions
2023-06-18 14:20 ` thetredev
2023-06-18 14:20 ` thetredev
2023-07-20 14:41 ` [ISSUE] [CLOSED] " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40861@inbox.vuxu.org \
--to=thetredev@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).