On Tue, Jan 29, 2013 at 1:22 PM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 29.01.2013 20:05, schrieb Michael Mol: > >> I'll note that in your version, you're ignoring the exit statuses of >> each of those commands. From a correctness standpoint, I prefer >> Stefan's version. > > Thanks ;-) > > Also thanks to Canek for the script-version ... I knew that way but > wanted to fully take advantage from the step-by-step approach my version > gives me. > > When I debugged my way up to the current draft it was helpful to see > which line/command failed etc.
That's my point; you don't need (and I would venture to say, you don't want) to debug this kind of stuff within systemd; you create your script, and you run it from the command line: $ /usr/local/bin/kvm-bridge start And see what is missing or what is failing; you debug it from here. When you have a working script, you just put it in a simple, concise systemd unit file, and everything should work (sans stuff like needing to put absolute paths for the executables, which BTW is easily solvable by putting PATH=/sbin:/usr/sbin in your /etc/conf.d/network_systemd file). But, for the last time: if it works, it works. I just think that's not the philosophy behind systemd; the idea is to find the proper solution. Using ExecStart= commands to debug when a "service" fails is as bad as putting echo statements in SysV/OpenRC scripts to see what is failing, IMO. Don't use the bad practices from SysV/OpenRC in systemd, I'm just saying. Just my opinion. But great to know is working. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
