Talk:SANE

If you have fixed a request make here can you remove the comments so we can see what is still to be done

use templates not templates-custom

create a smeserver-sane with the templates

see http://wiki.contribs.org/HylaFax for an alternative to a full reconfig/reboot, you just need to work out what needs to change

good work so far, I'm dusting off my old scanner...

---

Hi Cactus,

I don't understand:

 After succesfull of the required packages issue the following commands:
 
 signal-event post-upgrade
 signal-event reboot

It isn't very good, it takes of 'CPU time '

Ecureuil

What do you mean by that I do not understand your remark. Above commands are normal (required) steps after installing software using yum on the SME Server shell. - Cactus 05:41, 4 April 2008 (MDT)

Stick to SME Server default syntax and naming conventions please

Thank you for providing this Howto I think a lot of users will like this in the future, but I modified your English version and I noticed you have changed some items back. IMHO you should not have done so as I made changes to make things more conform to the SME Server naming conventions and you should have adapted them in your other translation(s) as well.

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). - 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.

Ecureuil