Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] prserv/serv.py: Better messaging when starting/stopping the server with port=0
Date: Fri, 18 Sep 2015 11:52:05 -0500	[thread overview]
Message-ID: <55FC4135.1080506@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LY5DQ9WQnf9N0T23+HZPrDaxF+pWBAfFAqJjEuS=yQnOg@mail.gmail.com>



On 09/17/2015 03:01 PM, Burton, Ross wrote:
> On 15 September 2015 at 15:59, <leonardo.sandoval.gonzalez@linux.intel.com>
> wrote:
>
>> +        sys.stderr.write("WARNING: Server is listening at port %s instead
>> of %s\n"
>> +                         % (rport,port))
>>
>
> I wouldn't call this a warning: port=0 means "pick your own", so it's not a
> warning that a different port was changed, it's useful information.

I add the WARNING string so user notices the new port taken. This info 
is important when trying to stop the server, but you are right, is not a 
warning, it should be just an info. Sending V2 right now.

>
> Ross
>


  reply	other threads:[~2015-09-18 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 14:59 [PATCH 0/3] PRServer: Fixes daemon issues leonardo.sandoval.gonzalez
2015-09-15 14:59 ` [PATCH 1/3] prserv/serv: Start/Stop daemon using ip instead of host leonardo.sandoval.gonzalez
2015-09-15 14:59 ` [PATCH 2/3] prserv/serv.py: Better messaging when starting/stopping the server with port=0 leonardo.sandoval.gonzalez
2015-09-17 20:01   ` Burton, Ross
2015-09-18 16:52     ` Leonardo Sandoval [this message]
2015-09-15 14:59 ` [PATCH 3/3] prserv/db: Use DELETE instead of WAL journal mode leonardo.sandoval.gonzalez
2015-09-17 20:01   ` Burton, Ross
2015-09-18 16:42     ` Leonardo Sandoval
2015-09-18 18:06       ` Leonardo Sandoval

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55FC4135.1080506@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox