On Sat, May 22, 2004 at 02:12:27AM -0400, Shashidhar SR wrote:
Shashidhar == Shashidhar [EMAIL PROTECTED] writes:
Shashidhar Hello,
Shashidhar I am Shashidhar SR Working for Siemens Communication
Shashidhar Software in Bangalore, INDIA as a Configuration
Shashidhar Manager for Clearcase.
Shashidhar I need some help regarding the samba configuration at
Shashidhar our site.
Shashidhar First Let me Explain our Environment:
Your question would be better answered on the ClearCase mailing list
See
http://www-136.ibm.com/developerworks/rational/
OR
http://www-106.ibm.com/developerworks/forums/dw_forum.jsp?forum=333cat=24hideBody=true
Shashidhar - We are Using samba 2.2.8a on Solaris 9. - We are
Shashidhar using samba as an interop from Solaris 9 box to
Shashidhar winnt/w2k/win-xp clients. - On Solaris we have
Shashidhar installed IBM Rational Clearcase and we have around 20
Shashidhar VOBs created.
Shashidhar Now we are successfully able to access the
Shashidhar files/directories which are stored on unix from
Shashidhar windows clients.
Shashidhar Some times we get an error saying Incorrect function
Shashidhar on the windows clients, when trying to access some
Shashidhar .txt/.cpp/.h or any other text files. and this error
Shashidhar is very sporadic, for some people it's works and for
Shashidhar others it dosen't, eventhough the permissions are same
Shashidhar for all the users.
This is usually a permission problem related to the ALBD service
account. It may also be due to a permission problem on the VOB storage
directories.
What does the view_log on the client say?
What does the samba log for the client say? Do you have
log file = /usr/local/samba/var/log.%m
in your smb.conf file? This will make it easier to debug by creating a
separate log file for each client.
I've attached a text file with some initial troubleshooting steps you
can follow. This file is extracted from some WEB pages I wrote about
setting up and configuring Samba for ClearCase.
--
Eric M. Boehm /\ ASCII Ribbon Campaign
[EMAIL PROTECTED] \ / No HTML or RTF in mail
X No proprietary word-processing
Respect Open Standards / \ files in mail
text_file_delta error
Unable to construct cleartext for object X in VOB
Error: Type manager text_file_delta failed construct_version
operation.
This is probably the most common error to occur in an interop
environment. The error is most likely due to a failure to map the ALBD
service account to a valid UNIX™ account.
The client may see this as the error message Incorrect Function.. The
error text above will be logged in the view_log on the view server host.
Steps to debug the problem
1.
Identify the ALBD service account. There are several methods that
can use used to find the account used to run the ALBD service.
1.
Windows NT 4.0
1. Select Start - Settings - Control Panel - Services
2. Double Click on the Atria Location Broker service
3.
Text Box This account contains the name of the ALBD
service account. service.
2.
Windows 2000/XP
1. Start - Run - services.msc
OR
Start - Settings - Control Panel - Administrative
Tools - Services
2. Double Click on the Atria Location Broker service
3. Click on Log On Tab
4.
Text Box This account contains the name of the ALBD
service account. service.
3.
All versions of Windows
1. Start - Run - regedit
2. Find key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Albd
3.
Value ObjectName contains the name of the ALBD
service account.
2.
Does the ALBD service account have a corresponding UNIX™ account?
1.
YES. Proceed to the next step
2.
NO. Check to see if the Samba username.map file contains an
entry to map the ALBD service account to a valid UNIX™
account that also has access to the VOB(s). See Configuring
username.map config_username_map.html for information on
how to set up this file.
If username.map has been modified, new connections will pick
up the changes. If you want to affect existing connections,
you will need to do one of:
1.
Send a HUP signal to all running smbd processes. This
will cause the smbd processes to reread the
configuration file. You must be root to send the signal.
kill -HUP `smbstatus -p`
2.
