commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Lohnes" <>
Subject RE: [PATCH][commons-daemon]Setting the process name
Date Thu, 10 Mar 2005 12:34:04 GMT
Thanks Simon.  I will add it to bugzilla.

-----Original Message-----
From: Simon Kitching [] 
Sent: Thursday, March 10, 2005 4:45 AM
To: Jakarta Commons Developers List
Subject: RE: [PATCH][commons-daemon]Setting the process name

On Mon, 2005-03-07 at 19:12 -0400, Derek Lohnes wrote:
> Has anyone had a chance to look at this?  Also did anyone get the
> file attached to the email?  I'm sure I attached it, but I just
> that the attachment I got with the email was a file containing
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> Thanks
> -----Original Message-----
> From: Derek Lohnes [] 
> Sent: Monday, February 28, 2005 11:46 AM
> To:
> Subject: [PATCH][commons-daemonSetting the process name
> I'm using the JSVC to run multiple java processes.  I would like to be
> able to tell them apart when viewing the process list.  Currently they
> all display as jsvc-exec.  The patch contains a new command line
> argument called procname.  If procname is passed as an argument to
> it is as the process name instead of the hardcoded 'jsvc.exec'.
> Also could you tell me when the next release would be available I'd
> prefer to use a released version of jsvc then a locally modified
> version, assuming this patch is accepted.

Hi Derek,

As there has not been any immediate response to this, I would suggest
that you creat a bugzilla entry and attach your patch there. That way
things won't get lost, and the issue will be visible whenever anyone
does a search on open bugs for commons-daemon.

I expect that commons-daemon has a fairly small pool of committers (it
involves JNI code which is not a hugely popular area) and I suspect
building/testing new releases is a significant effort as it involves
getting access to multiple OSes. Because of these, I would guess that
response to your patch may be slow.

After the bugzilla entry has been created, I recommend posting a polite
reminder every fortnight or so (to the bugzilla entry or direct to this



To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message