254
edits
Changes
Jump to navigation
Jump to search
Line 29:
Line 29: + + + + + + + + + + + + + + + + +
no edit summary
A service normally is a daemon, hence the database record should be named saned (or sane) and not sane-port. On top of that I think it is also strange to call the group the server is configured to use to be saned, I therefore changed it to ''saneusers'' in the example to avoid confusion between users and the SANE daemon (which is normally referenced as saned).
A service normally is a daemon, hence the database record should be named saned (or sane) and not sane-port. On top of that I think it is also strange to call the group the server is configured to use to be saned, I therefore changed it to ''saneusers'' in the example to avoid confusion between users and the SANE daemon (which is normally referenced as saned).
- [[User:Cactus|Cactus]] 05:49, 4 April 2008 (MDT)
- [[User:Cactus|Cactus]] 05:49, 4 April 2008 (MDT)
:: I don't speak english very good
:: Do not change anything without understanding and reading
:: View sane documentation: service = sane-port => grrrrrrrrrrrrrrr
:: http://www.sane-project.org/man/saned.8.html
:: http://penguin-breeder.org/sane/saned/
:: thank you
::
:: Another problem:
:: If xinetd start, ' saned - d128 ' will not be able to work
:: I prefer the French version for it.
::
:: for signal-event post-upgrade and signal-event reboot:
:: The post upgrade and the reboot process are only needed for smeserver
:: packages using the template system. As sane-backend nor xinetd are
:: smeserver specific, we don't need these (expensive !) steps.
:: [[User:Ecureuil|Ecureuil]]