How to avoid data corruption when running remote ConsoleOne against domain data store at Linux
This document (3036467) is provided subject to the disclaimer at the end of this document.
The resolution depends on the platform of the workstation that ConsoleOne is running on, and the type of connection that the workstation has with the Linux server.
If the Linux server is OES, you will need to turn on "CROSS PROTOCOL LOCKS" on the OES server. Enabling this lock will make OES recognize file lock issues through both SAMBA and NCP client connections. This lock can be enabled through ncpcon. In ncpcon, type "set CROSS_PROTOCOL_LOCKS=1" or add this line "CROSS_PROTOCOL_LOCKS 1" to the /etc/opt/novell/ncpserv.conf file. There is a limitation to this too, it only applies to Windows workstations. The Novell Client for Windows allows the NCP protocol to correctly enforce this. The Novell Client for Linux does not have this functionality yet.
If the Linux server is SLES, and the connection is SAMBA, meaning ConsoleOne is running on a Windows workstation, run the GroupWise 7.0.2 or newer code. This has been modified to enforce the advisory lock.
Note: Do not run Linux version of ConsoleOne on a remote Linux server or SLED until the Novell Client for Linux defect is fixed.
Note: Do not run Linux version of ConsoleOne on remote Linux workstation using NFS connection to the Linux server.
Our intention is for the next generation of GroupWise
administration to use its own client/server technology to eliminate
the problems above.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3036467
- Creation Date:18-JUN-07
- Modified Date:26-APR-12
Did this document solve your problem? Provide Feedback