On Thu, Jun 14, 2012 at 02:03:05PM -0400, Brian K. White wrote:
Also there is this. Recently on the rsync bugzilla someone posted a bug because rsync exits with exit values other than 0 in some situations that are not errors. These exit values are documented and perfectly reasonable. But, systemd does not allow for _anything_ but 0=ok, everything else = failure, which screws up systemd stopping/starting the service sometimes. Systemd says rsync is wrong and should change that behavior. The behavior is documented, has been the same for decades, predates systemd by decades, and is within the designed intended use of exit values in programs since exit values even existed. Yet systemd, instead of realising that such a narrow assumption is a bug, once again decides the rest of the world is wrong and systemd is right. That tells me that I do not want to invest any time adapting anything to systemd, because it's too much of a one way street. Systemd will not adapt to provide me with a powerful tool that can handle any possible situation, systemd requires me to adapt everything else to get it to work at all, or live without anything I can't adapt.
Why would you ever use a 'raw' rsync call as a system service that systemd would want to run? Surely you would properly wrap it to handle the different types of errors that rsync can produce, right? Anyway, that's way off topic here, we understand you don't like systemd, and that's sad, but there are always other distros, that for today, are not upgrading. Nothing is set in stone for forever though, I place bets on everyone moving in the next 5 years :) good luck, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org