I'm running Ubuntu 18.04 LTS. Yes there is a iscsid.socket there that is active.
So from what you said, I think I don't need to enable iscsid.service so that it's started at boot time, given that my iscsi usage is intermittent. THanks you lots for the clarification David On Sunday, 4 November 2018 17:36:58 UTC, The Lee-Man wrote: > > What distro are you running? The iscsid daemon has been set up for what > systemd calls "socket activation" in the upstream sources. > > For example, for SUSE, we have another service called iscsid.socket. For > socket activation, you need a "SERVICE.socket" unit, and a > "SERVICE.service" unit. > > For this to work, you must have the "socket" unit running and do not need > the regular service running. This means that systemd will watch the network > socket you specify, and start up your service if somebody tries to reach > it, which in turn means iscsid does not have to be running all the time. > This is particularly useful if you rarely use the service, but it's not > smart enough to stop the daemon when you're no longer using it. So once it > starts up, it stay running, and "systemctl status SERVICE" will show that > it is running. If you run "systemctl stop SERVICE", it will stop it (i.e. > the iscsid daemon in this case) but warn "can be started again by > SERVICE.socket" (or something like that). > > In answer to your question, there is nothing wrong with enabling the > service by default if you use it regularly. But if you have an > "iscsi.socket" file on your system, then you do not *have* to have iscsid > running to be able to use it. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
