Bug 3311 - hg serve won't start as a daemon with web-conf file on Windows
Summary: hg serve won't start as a daemon with web-conf file on Windows
Status: RESOLVED WORKSFORME
Alias: None
Product: Mercurial
Classification: Unclassified
Component: hgweb (show other bugs)
Version: unspecified
Hardware: PC Windows
: normal bug
Assignee: Bugzilla
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-07 03:26 UTC by Marcel Svitalský
Modified: 2012-07-29 18:33 UTC (History)
4 users (show)

See Also:
Python Version: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel Svitalský 2012-03-07 03:26 UTC
On Windows XP, with Mercurial 2.1.1 (and 2.1 earlier), when I go into some
repository and issue either "hg serve" or "hg serve -d" they both work all
right, but when I try "hg serve --web-conf c:\somepath\hgwebrc" it only
works as non-daemon. With "-d" option it crashes immediately with "abort:
child process failed to start" error message.

The hgwebrc file is as simple as this:

[web]
style = monoblue
address = localhost

[paths]
/mercurial/repo = c:\develop\repo
Comment 1 Patrick Mézard 2012-04-15 05:18 UTC
Works for me with default tip, on WinXP, local VS2008 build. Here is my test
script:

"""
C:\dev\mercurial>mkdir parent
C:\dev\mercurial>cd parent
C:\dev\mercurial\parent>hg init repo
C:\dev\mercurial\parent>cd repo
C:\dev\mercurial\parent\repo>echo a > a
C:\dev\mercurial\parent\repo>hg ci -Am adda
adding a
C:\dev\mercurial\parent\repo>cd ..
C:\dev\mercurial\parent>copy CON hgweb.conf
[paths]
/mercurial/repo = c:\dev\mercurial\parent\repo
^Z
        1 file(s) copied.

C:\dev\mercurial\parent>hg serve -d --web-conf hgweb.conf
C:\dev\mercurial\parent>curl http://localhost:8000 | grep repo
<title>Mercurial repositories index</title>
<td><a href="/mercurial/repo/">mercurial/repo</a></td>
"""

I can browse the repository. I suppose this is an executable/toolchain issue.
Comment 2 Bugzilla 2012-05-12 09:28 UTC

--- Bug imported by bugzilla@serpentine.com 2012-05-12 09:28 EDT  ---

This bug was previously known as _bug_ 3310 at http://mercurial.selenic.com/bts/issue3310