Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#708184: collab-qa/cloud-scripts/masternode: Add support for specifying output directory
1 view
Skip to first unread message
Nathaniel Harrison Handler
May 13, 2013, 4:40:02 PM5/13/13
to
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
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.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
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
David Suárez
May 17, 2013, 4:20:02 PM5/17/13
to
On Lunes, 13 de mayo de 2013 22:37:30 Nathaniel Harrison Handler escribió:
> 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
Hi,
> 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
Patch attached.
David
Lucas Nussbaum
May 18, 2013, 3:40:02 AM5/18/13
to
On 18/05/13 at 00:10 +0200, David Su�rez wrote:
> On Lunes, 13 de mayo de 2013 22:37:30 Nathaniel Harrison Handler escribi�:
Looks good. I've added you to the collab-qa project on alioth (assuming
deiv-guest is your login). Could you commit the patch?
Thanks
Lucas
> On Lunes, 13 de mayo de 2013 22:37:30 Nathaniel Harrison Handler escribi�:
> > 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
>
> Hi,
>
> Patch attached.
Hi,
> > 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
>
> Hi,
>
> Patch attached.
Looks good. I've added you to the collab-qa project on alioth (assuming
deiv-guest is your login). Could you commit the patch?
Thanks
Lucas
David Suárez
May 18, 2013, 9:40:01 AM5/18/13
to
On Sábado, 18 de mayo de 2013 09:35:13 Lucas Nussbaum escribió:
> On 18/05/13 at 00:10 +0200, David Suárez wrote:
thats no problem. Im educating about alioth. When Im ready I commit them.
David
> On 18/05/13 at 00:10 +0200, David Suárez wrote:
> > On Lunes, 13 de mayo de 2013 22:37:30 Nathaniel Harrison Handler escribió:
> > > 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
> >
> > Hi,
> >
> > Patch attached.
>
> Hi,
>
> Looks good. I've added you to the collab-qa project on alioth (assuming
> deiv-guest is your login). Could you commit the patch?
>
> Thanks
>
> Lucas
Hi,
> > > 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
> >
> > Hi,
> >
> > Patch attached.
>
> Hi,
>
> Looks good. I've added you to the collab-qa project on alioth (assuming
> deiv-guest is your login). Could you commit the patch?
>
> Thanks
>
> Lucas
thats no problem. Im educating about alioth. When Im ready I commit them.
David
Debian Bug Tracking System
May 23, 2013, 8:00:02 AM5/23/13
to
Your message dated Thu, 23 May 2013 13:55:51 +0200
with message-id <2013052311...@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 ow...@bugs.debian.org
immediately.)
--
708184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
with message-id <2013052311...@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 ow...@bugs.debian.org
immediately.)
--
708184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
david suarez
May 23, 2013, 8:00:02 AM5/23/13
to
0 new messages