On Tue, Jul 20, 2010 at 12:41:11AM +0200, Hans de Goede wrote: > >> I think the problem was that the iscsid service was on by default, so > >> when things like libvirt install it iscsid would always start but many > >> times not be needed. > > > > In a systemd world we can fix this in a much nicer way: > > libvirtd.service would just have a "Wants: iscsid.service" in it. That > > way when libvirtd is started iscsid is started too. And if people use > > iscsid in other areas too they can just add a single symlink > > (/etc/systemd/system/multi-user.target.wants/iscsid.service → > > /lib/systemd/system/iscsid.service) and it is started on boot, regadless > > whether libvirtd is enabled or not. > > I'm afraid that is not how the relation between libvirt and > iscsi-initiator-utils works. I don't know exactly what libvirt needs > iscsi-initiator-utils for, but I think it does not require > iscsid to be running. I guess we need to involve one of the > libvirt guys into this discussion to tell us what exactly libvirt uses > iscsi-initiator-utils for. libvirt doesn't directly care about iscsid at all. It just issues commands using iscsiadm to login/out of targets & query LUNs, etc. If iscsiadm requires that iscsid be running in order to work, then I guess it should activate it when required ? Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
