First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 193935
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Daniel Black <dragonheart@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Dennis Schridde <devurandom@gmx.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
monotone.initd.patch Proposed patch patch Dennis Schridde 2007-09-27 00:28 0000 687 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 193935 depends on: Show dependency tree
Bug 193935 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-09-27 00:27 0000 
When I try to start /etc/init.d/monotone inside /root/, it tries to access
/root/_MTN, which it doesn't have permissions for since it is started with
UID=monotone. Since mtn "thinks" the workspace is critical, it will immediately
exit. (Upstream is thinking about changing that behaviour in future versions.)

The attached patch works around the issue by cd'ing to monotone's $HOME and
calling mtn from there.

Reproducible: Always

Steps to Reproduce:
1. cd to a directory inaccesible to the monotone user, eg. /root/
2. Issue /etc/init.d/monotone start

Actual Results:  
Mtn starts and immediately exits again, notable by the entry in the logfile

Expected Results:  
Mtn stays "alive".

------- Comment #1 From Dennis Schridde 2007-09-27 00:28:25 0000 ------- 
Created an attachment (id=131986) [details]
Proposed patch

------- Comment #2 From Christian Faulhammer 2007-10-07 12:33:05 0000 ------- 
fixed in 0.36
First Last Prev Next    No search results available      Search page      Enter new bug