openstack team mailing list archive

["Dugger, Donald D" <donald.d.dugger@xxxxxxxxx>]

I'd vote for having daemonize as an option at best.  In a development environment it's very nice to be able to kill all processes just by terminating the `screen' ( or `tmux') session rather than having to kill all the daemons individually.  Plus it's nice to be able to see the current output from each process without having to worry about data that is still stuck in output buffers.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786

From: openstack-bounces+donald.d.dugger=intel.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+donald.d.dugger=intel.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ghe Rivero
Sent: Wednesday, February 08, 2012 11:54 AM
To: Joshua Harlow
Cc: openstack
Subject: Re: [Openstack] Devstack (sh) and tmux

I like the idea of demonize it. Everyone using devstack should be able to open a terminal and use tail in the logs to see what's going on. Or maybe an option can be added to devstack to choose daemon vs. screen . BTW I use tmux+bash
Ghe Rivero
On Wed, Feb 8, 2012 at 7:24 PM, Joshua Harlow <harlowja@xxxxxxxxxxxxx<mailto:harlowja@xxxxxxxxxxxxx>> wrote:
Why not just daemonize the processes ;)
This is pretty much what I am doing in devstackpy and it seems to work pretty well.
I think people are pretty familiar with PID files, and files which contain stderr/stout as this is how a lot of other unix stuff runs.


On 2/8/12 9:45 AM, "Jesse Andrews" <anotherjesse@xxxxxxxxx<http://anotherjesse@xxxxxxxxx>> wrote:
the reason for adding tmux is that we were running into issues with
services not launching inside screen (due to a timing issue).

I'm for removing tmux - since the sleep between creating a screen &
using it has resolved the issue.

Jesse

On Wed, Feb 8, 2012 at 9:39 AM, Jay Pipes <jaypipes@xxxxxxxxx<http://jaypipes@xxxxxxxxx>> wrote:
> On 02/08/2012 11:44 AM, Chmouel Boudjnah wrote:
>>
>> Hi,
>>
>> As mentioned in bug #928967[1] tmux support in devstack is not working
>> and I was wondering if there was much people using it and if I should
>> fix it. The advantage of tmux support is aside of being arguably a
>> better terminal wm it allows support for different shells than bash (ie:
>> zsh) for devstack as reported in bug #928883[2].
>>
>> What do you think? Is anyone using much tmux or other shells than bash
>> with devstack.
>
>
> Nope, I only use bash...
>
> -jay
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx<http://openstack@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx<http://openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



--
Ghe Rivero
OpenStack & Distribution Engineer
www.stackops.com<http://www.stackops.com/> |  ghe.rivero@xxxxxxxxxxxx<mailto:diego.parrilla@xxxxxxxxxxxx> | +34 625 63 45 23 | skype:ghe.rivero
<http://www.stackops.com/>

[http://stackops.s3-external-3.amazonaws.com/STACKOPSLOGO-ICON.png]

******************** ADVERTENCIA LEGAL ********************
Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley.

***************** PRIVILEGED AND CONFIDENTIAL ****************
We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law.