Am 29.01.2013 20:33, schrieb Canek Peláez Valdés: > On Tue, Jan 29, 2013 at 1:22 PM, Stefan G. Weichinger <li...@xunil.at> wrote: >> 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.
Ok, I understand your approach. > 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). Yep, thanks. > 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. Thanks for sharing ... I quickly followed your suggestions and built another service-file with your solution (you had typos btw -> "brigdge" ;-) ). It works as well and is maybe even slimmer in execution. I will just keep both versions around and see where it gets me. Thanks, Stefan
