[Mono-bugs] [Bug 75724][Min] New - mono-service usage info says
.log instead of .lock
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Fri Aug 5 11:54:50 EDT 2005
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by michael at synthesyssolutions.com.
http://bugzilla.ximian.com/show_bug.cgi?id=75724
--- shadow/75724 2005-08-05 11:54:50.000000000 -0400
+++ shadow/75724.tmp.24024 2005-08-05 11:54:50.000000000 -0400
@@ -0,0 +1,43 @@
+Bug#: 75724
+Product: Mono: Tools
+Version: 1.1
+OS: GNU/Linux [Other]
+OS Details:
+Status: NEW
+Resolution:
+Severity:
+Priority: Minor
+Component: tools
+AssignedTo: mono-bugs at ximian.com
+ReportedBy: michael at synthesyssolutions.com
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: mono-service usage info says .log instead of .lock
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+mono-service usage information reports that the default lock file is
+'/tmp/<service>.log'. In reality the default is the more sensible:
+'/tmp/<service>.lock'.
+
+Steps to reproduce the problem:
+1. Open console
+2. Type in 'mono-service'
+3. Notice line that begins with '-l:<lock file>' lists .log as the default
+4. Start a service using 'mono-service <service-name>'
+
+Actual Results:
+A lock file called '<service-name>.lock' is created.
+
+Expected Results:
+'<service-name>.log' according to the docs, but .lock makes more sense.
+
+How often does this happen?
+Every time
+
+Additional Information:
+I believe the responsible file is:
+http://svn.myrealbox.com/viewcvs/trunk/mono/scripts/mono-service.in
More information about the mono-bugs
mailing list