vl-messaging configuration readme
fedoseev at ru.ibm.com
Wed Jun 21 13:55:56 GMT 2006
Alexander, could you add this text as a readme/example to the
vl-messaging branch now has different messaging implementations. One can
switch messaging type with compile-time options and smb.conf parameters.
1) Run-time options
messaging type = one of (tdb, dgram, stream, dispatcher)
* tdb - classic one. old messages.tdb implementation [default]
* dgram - unix datagram sockets implementation (based on samba 4
ideas) - each process owns a socket in var/locks/messaging/ directory,
messages are written direclty into the corresponding socket.
* stream - unix stream sockets implementation - each process owns a
(stream) socket in var/locks/messaging/ directory. This implementation
implies lot of connections between processes (peer-to-peer).
* dispatcher - each system has its own dispathcer process (is's forked
from the first smbd/nmbd process), each process connects to the
dispatcher and sends messages through it. If system has several nodes,
dispatchers transfer messages between them via tcp (this needs
clusterwide code - see below).
'dispatcher' type options:
messaging address = ip address [default is 127.0.0.1]
messaging network = ip address / network mask [default is 127.0.0.1/8]
messaging port = ip port [default is 51000]
Network parameters of the tcp messaging. Dispatcher daemon listens on
'messaging address':'messaging port' and allows connections only from
'messaging network'. This parameters is used only if clusterwide
messaging has been compiled in (see below).
2) Compile-time options
If you turn on this option, clusterwide tcp-based messaging will be
compiled in. Process id structure is exnedned with ip address. In fact,
these changes affect only if 'dispatcher' messaging is selected.
Linux Center of Competence, IBM EE/A
IBM Linux Technology Center: Samba Team
Phone: +7495 775-8800 x 2133
More information about the samba-technical