![](https://seccdn.libravatar.org/avatar/45bf5eef0471996074efa055ea252116.jpg?s=120&d=mm&r=g)
El vie 12 abr 2013 17:01:00 CLST, Claudio Freire escribió:
On Fri, Apr 12, 2013 at 4:40 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
rcfoo start|stop
- meaningless or confusing the the unit file has RefuseManualStart or RefuseManualStop set, I assume you dont want to restrict usage of unit file options in order to preserve this illusion of compatibility do you ?
Why would it be meaningless?
It would tell you it refused to start|stop. That's all.
Yeah, but users expect sysvinit behaviour.. where there was no such thing as refusing to start or stop BECAUSE the init script said so, distinct from an error, misconfiguration.. This are the return values : # Return values acc. to LSB for all commands but status: # 0 - success # 1 - generic or unspecified error # 2 - invalid or excess argument(s) # 3 - unimplemented feature (e.g. "reload") # 4 - user had insufficient privileges # 5 - program is not installed # 6 - program is not configured # 7 - program is not running # 8--199 - reserved (8--99 LSB, 100--149 distrib, 150--199 appl) start , stop cannot fall under 3 "unimplemented" since those are mandatory under this old arse scenario :-P
In any case, in those cases the package is configured as you say it's meaningless. We're all assuming discretionary judgement by the packager.
Problem is rpmlint does not have discretionary judgement. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org