Am 29.01.2013 20:23, schrieb Canek Peláez Valdés: > I really believe the most important thing abount systemd unit files is > that they are small and simple. You can also check the exit status > from each command in the script, or even better, you can do a test > after all the commands are done to check the status of the bridge and > see if it was created correctly. > > None of this belongs in the unit service, IMO. Otherwise, you end > creating ssh keys and user groups in unit files, and none of this > belongs there. Clear separation between the services and the init > system. > > But of course, as I said to Stefan, if it works it works.
As I mentioned it is a first version ... just to make things work. If all the services/daemons/stuff work with systemd then I am able to use it as default init-system here and I don't have switch back to openrc to do my work (for example when I need KVM-based virtualization on my workstation). I agree with your argument that unitfiles should be as small and simple as possible, on the other hand those commands just get pulled in from elsewhere: the complexity is just moved out of sight, right? I did quite some research to find more elegant solutions ... so far I wasn't successful. For now I am happy to get my itches scratched ... I am absolutely ready to learn and improve things. Sharing my first steps here maybe helps to motivate other gentoo-users to give systemd a try? Regards, Stefan
