As long as that user can talk to the printers' device nodes (and/or the network), it needn't so far as I know. The original "system daemon vs. user program" di

As long as that user can talk to the printers' device nodes (and/or the network), it needn't so far as I know. The original "system daemon vs. user program" dichotomy offers a much broader range of interpretations than this, though, and it was more the implication of "this can and should be an evanescent program invoked by individual users, implicitly persisting little or no state between invocations" to which I sought to object. (That said, I take another nearby commenter's point regarding the need, and existence, of a more evanescent and safer option on systems that will never see more printing than one user does two or three times a year.)