Hi all,
I have been testing TortoiseHg on Windows 7 x64 and have come up against a
small issue. My repo's live on my home directory which is mounted via samba.
When I modify the hgrc config file via TortoiseHg I get an error saying "[Error
32] The process cannot access the file because it is being used by another
process"
Btw, I am using the latest TortoiseHg (2.1.3).
In my initial investigations, I have found that TortoiseHg is successful in
creating a temp hgrc file (called something like .hgrc-3aa3es) and the problem
comes when it attempts to delete the old hgrc and rename the temp. If I attempt
to modify the config through the settings screen, I get the following bug
report.
{{{
#!python
** Mercurial version (1.9.2). TortoiseHg version (2.1.3)
** Command: --nofork workbench
** CWD: H:\Hg\Quantified_docs
** Encoding: cp1252
** Extensions loaded: convert
** Python version: 2.6.6 (r266:84297, Aug 24 2010, 18:13:38) [MSC v.1500 64 bit
(AMD64)]
** Windows version: (6, 1, 7601, 2, 'Service Pack 1')
** Processor architecture: x64
** Qt-4.7.1 PyQt-4.8.3
Traceback (most recent call last):
File "tortoisehg\hgqt\settings.pyo", line 847, in accept
File "tortoisehg\hgqt\settings.pyo", line 825, in applyChanges
File "tortoisehg\hgqt\settings.pyo", line 1172, in applyChanges
File "tortoisehg\util\wconfig.pyo", line 244, in writefile
File "mercurial\util.pyo", line 744, in rename
File "mercurial\windows.pyo", line 263, in rename
WindowsError: [Error 32] The process cannot access the file because it is being
used by another process
}}}
My samba conf is as follows.
[global]
delete readonly = Yes
workgroup = WORKGROUP
guest account = smbguest
server string = %h server
dns proxy = no
name resolve order = lmhosts host wins bcast
interfaces = 127.0.0.0/8 eth0
log level = 2
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
security = user
map to guest = Bad Password
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n
*password\supdated\ssuccessfully* .
pam password change = yes
domain logons = yes
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
hide dot files = No
unix extensions = no
I am not using Mercurial over Samba as a shared repository, I just have limited
space on my workstations (due to SSD's) and prefer to have the working
environments sitting on a nas. The main reason I want to preserve this setup is
for ease in setting up the symlinks for the development server.
Has anyone else faced this issue? I am happy enough if this issue will only
affect modification of the hgrc file, but I am worried that it may strike again
on something more important down the line.
Thanks
Quinn
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
