Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upsetproctitle() support for DragonFly #15703
Comments
From @pavalosCreated by @pavalosDragonFly has the same setproctitle() support that FreeBSD has, so Perl Info |
From @jkeenanOn Thu, 10 Nov 2016 19:29:16 GMT, peter@theshell.com wrote:
1. Do you know if there is someone who is the designated "Perl 5 maintainer" for DragonflyBSD? 2. Is there someone who is capable of smoke-testing Perl 5 blead on this OS, and/or is capable of running a CPANtesters operation for DragonflyBSD? I ask these questions because any patch to the hints file will need to be confirmed as not causing harm. We know that we (Perl 5 Porters) are already not doing a great job on testing the long established BSDs (Free, Open, Net), but at least in two of those three cases we know whom to call. Any leads you can provide would be appreciated. Thank you very much. -- |
|
The RT System itself - Status changed from 'new' to 'open' |
From @jkeenanOn Sat, 19 Nov 2016 23:05:36 GMT, jkeenan wrote:
No responses in over a month. Marking ticket stalled. -- |
|
@jkeenan - Status changed from 'open' to 'stalled' |
From @jhiSorry, I don't have DragonFly setup. But a general comment about the desire of having a regular smoketester for all supported platforms. It's a fine desire. Certainly would help in blead not accidentally breaking on various platforms. But for rarer platforms, it is not going to happen. One can chase down people who in the past have provided patches on the platforms, or reported bugs, and try to get them to do if not Continuous Integration, at least semi-regular builds, automated and/or regular if possible. Another possible avenue of finding people who care is to look for the whatever packaging |
|
The RT System itself - Status changed from 'stalled' to 'open' |
From @xsawyerxOn 12/30/2016 01:55 AM, Jarkko Hietaniemi via RT wrote:
This is basically the summary of it. We simply do not have active
Another avenue is to have a system that sets up virtual environments
Which goes back to reporters, I believe. From my perspective, tickets that have to do with a platform on which we While I do not want to close the ticket, I also do not want to keep In this case I believe a grace period for such tickets, as Jim promotes |
From @jkeenanOn 12/30/2016 05:22 AM, Sawyer X wrote:
I marked the ticket Stalled. That's a category I'm loathe to use, as it |
From @iabynOn Fri, Dec 30, 2016 at 08:20:26AM -0500, James E Keenan wrote:
But in this case we weren't waiting on the OP to supply information, we However, I would request the following clarifications from the OP. In S_set_dollarzero(), it decides whether to call setproctitle() based on OP: is HAS_SETPROCTITLE set on DragonFly systems? Secondly, it calls setproctitle() with a 1st arg of either "-%s" or Even better, could OP supply a patch that works under DragonFly? -- |
From @pavalos
Yes.
For DragonFly it should be “-%s”, just like the __FreeBSD_version > 410001 case.
Inline Patch--- mg.c.orig 2016-12-26 04:49:24.000000000 -0800
+++ mg.c 2017-01-02 22:26:14.683427000 -0800
@@ -2557,7 +2557,7 @@
* the setproctitle() routine to manipulate that. */
if (PL_origalen != 1) {
s = SvPV_const(sv, len);
-# if __FreeBSD_version > 410001
+# if __FreeBSD_version > 410001 || defined(__DragonFly__)
/* The leading "-" removes the "perl: " prefix,
* but not the "(perl) suffix from the ps(1)
* output, because that's what ps(1) shows if the |
From @iabynOn Mon, Jan 02, 2017 at 10:33:53PM -0800, Peter Avalos wrote:
Thanks, applied to blead as v5.25.8-178-g3862695. That commit also -- |
|
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130068 (status was 'resolved')
Searchable as RT130068$