On 27/03/18 15:06, Aaron Conole wrote: > There are a few advantages (and some disadvantages, also). > > One thing that's nice is systemd will clean up the directories when the > service ends. I realize that /run is usually tmpfs, but it's nice that > they don't linger - even if ovs-lib "breaks in the middle" (meaning > something goes wrong .. though I'm unable to name an instance where I > observed that). Actually, I am looking at tmpfiles.d entries for > managing some of these complicated directory lists (like /dev/hugepages, > etc). >
I agree, tmpfiles.d is probably going to simplify things a bit. > Another advantage is when we fully hook up with the > user+group+capabilities (it's on my TODO list) in systemd service > files. At that point, it will not be possible for the ovs-lib to create > the runtime directories. > > Of course, we know the biggest disadvantage - if systemd breaks things, > they are really broken. > > Does it make sense? > Yes thank you very much -- markos SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev