El 23/10/13 15:10, Lee Duncan escribió:
Advice? Answers?
Ok, I just looked at the patch that implements this bits, some comments...
- systemd unit files are NOT and should never be marked as %config
- why is LOCK_DIR defined in the command line as /etc/iscsi ? that does not look quite right.. use /run/lock/iscsi and provide a tmpfiles.d snippet with d /run/lock/iscsi 0700 root root -
- about starting the service only when needed.. if the presence of an iscsi device happens to trigger a kernel event you could detect such change with udev , create an appropiate rule and use TAG+="systemd", ENV{SYSTEMD_WANTS}+="yourservice.service" to automagically start the needed stuff on demand. I have never used iscsi so I have no idea if this the case.
- iscsid.service is missing an "Also=iscsid.socket" in the [Install] section