Repository navigation
Conversation
TODO: list build-time default for RC_PATH
| .Dd $Mdocdate$ | ||
| .Dt openrc-intro 7 | ||
| .Os | ||
|
|
There was a problem hiding this comment.
mandoc will render these empty lines as empty lines, so the man page has lots of empty lines.
Use a line with . instead, which yields the visual separation that you want in the source without affecting how the page is rendered.
There was a problem hiding this comment.
oh, mandb ignores them (which i was using to test) but mandoc proper doesn't, wonderful
will fix
| .Os | ||
|
|
||
| .Sh NAME | ||
| .Nm openrc-intro |
There was a problem hiding this comment.
File name does not match this name.
| openrc requires that every service provides the | ||
| .Ic start Ns () , | ||
| .Ic stop Ns () , | ||
| and | ||
| .Ic status Ns () | ||
| commands. |
There was a problem hiding this comment.
This is a misleading start if the next paragraph indicates that users shouldn't define custom start/stop for the common case.
When should these actually be defined by the user?
There was a problem hiding this comment.
that was meant to be covered by Do not define custom start or stop functions for managing daemons, though i see what you mean
we could have it say openrc always provides start(), stop() and status() commands to every service, then add a section later going more in detail about custom commands?
2 participants
those are also aimed to be rendered to html as static online docs later