FS#61899 - [parallel] Process name of parallel should be parallel instead of perl

Attached to Project: Community Packages
Opened by Yichao Zhou (zhou13) - Saturday, 02 March 2019, 09:18 GMT
Last edited by Balló György (City-busz) - Monday, 18 March 2019, 08:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Process name of parallel should be parallel instead of perl.

This can be done by changing #!/usr/bin/env perl to #!/usr/bin/perl in /usr/bin/parallel

Additional info:
* package version(s)
community/parallel 20181222-1

Steps to reproduce:
1. $ parallel sleep 10 ::: 1
2. $ killall parallel
parallel: no process found
This task depends upon

Closed by  Balló György (City-busz)
Monday, 18 March 2019, 08:01 GMT
Reason for closing:  Upstream
Comment by loqs (loqs) - Saturday, 02 March 2019, 14:12 GMT
As the #! invocation is supplied by upstream http://git.savannah.gnu.org/cgit/parallel.git/tree/src/parallel?id=fd4694c66b93f87b9068f84fa70ffb37812e2e48#n1
have you contacted upstream about the issue?
Comment by Yichao Zhou (zhou13) - Saturday, 02 March 2019, 23:15 GMT
Initially I want to report it upstream. However, I think "#!/usr/bin/env perl" gives maximum compatibility across different distribution/environment, which make it the safest choice in upstream. In Archlinux, the location of perl is fixed. Therefore, changing it to "#!/usr/bin/perl" here seems to be a more reasonable choice.
Comment by Eli Schwartz (eschwartz) - Sunday, 03 March 2019, 07:44 GMT
You could make the very same argument that all other distributions/environments should "fix" the location, and extending that logic, perhaps upstream should make this configurable or autodetected at installation time...

But I'm sure there are many thousands of scripts installed by Arch Linux, AUR packages, or manually, which contain shebang lines that are, arguably, completely correct, but show up as the wrong process or whatever. Should we modify all those too, because upstream has made the wrong decision?

I would advise instead using pkill -f which is a lot more flexible than killall. It is more scalable, works everywhere without requiring modifications to packages, etc.

Loading...