Hi Michal, Michal Lesiak wrote on Sun, Apr 27, 2014 at 12:01:54PM +0200:
> I know, but I'll never know what ancient versions my users will use, > so I'm using a (reasonably) old version to build the package and > compile stuff to retain some backwards-compatibility. That's not a good plan at all. Sometimes, new binaries work on old versions and vice versa, but in general, that's not the case. So if you ship packages for 5.2-stable (well, actually, 5.2-obsolete), you force your users to use 5.2-obsolete. Not so great. For example, if one of your users chooses to run 5.5 (which would be a good idea), your 5.2 packages will *not* run on that at all. > About the echo, I know about -d option, but that's not the case here. > My question here is broader - what's the OpenBSD's policy in such case? > If the daemon started by the rc.script fails, should it display some > information about that That's not easily possible: Each daemon works in a different way. Some print to stdout, some to stderr, some to syslog, some always print something, even when successful, some only print anything in case of failure and so on and so forth - there is no one size that fits all. And even if the rc.d(8) system does realize that something failed, it cannot easily get messages back that were printed before and already discarded. > or is "Foo(failed)" enough information for a typical OpenBSD user? Usually not, to debug a failure, you often need more than that. But it's sufficent to understand that there was some kind of a failure, so you can re-run with the -d option and look at the output in detail. Yours, Ingo
