Bug#708184: marked as done (collab-qa/cloud-scripts/masternode: Add support for specifying output directory)
Your message dated Thu, 23 May 2013 13:55:51 +0200
with message-id <20130523115551.GA2764@xanadu.blop.info>
and subject line Re: Bug#708184: collab-qa/cloud-scripts/masternode: Add support for specifying output directory
has caused the Debian Bug report #708184,
regarding collab-qa/cloud-scripts/masternode: Add support for specifying output directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
708184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708184
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: wishlist
Currently, when the masternode script is run, logs are copied to /tmp/logs automatically. It would be nice to support specifying an alternate directory for the logs. This would allow multiple instances of masternode to run simultaneously on the same machine without interfering with each other.
-- System Information:
Debian Release: 6.0.7
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On 23/05/13 at 13:52 +0200, david suarez wrote:
> Should I close the bug ?
Fixed by commit 0480a6e6a39dd2ee876e6d222a45c25d240968a8 from David
Suarez.
Lucas
--- End Message ---
Reply to: