According to the samba howto collection, dynamic load balancing seems to be
a bad solution : one printer should have only one queue.
If you want to have failover : usually a shared disk is used. The disk is
mounted by the active machine. On this disk, you may have all your
executables and config files, and spool space. You may start the daemons
with a script (problem with swat).
The names of the queues should be the same on the 2 machines. (the same, the
better : hard / soft / users) Of course one instance of samba should be
working at a time.
It's better if you are able to take the IP of the failed machine. If you
have no shared disk, may be regular copy of all the files is sufficient.
Your problem is not only a printer problem, it's a general samba failover
problem.
My 2cts.
HTH.
"Tim" <[EMAIL PROTECTED]> a écrit dans le message de
news:[EMAIL PROTECTED]
> I should add that we have no intention of using these servers for file
sharing
> (except for the hidden print$ share). These are strictly print servers.
>
> I noticed Red Hat Cluster Manager states it doesn't support failover of
printer
> shareshow come?
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
