Date: Sat, 6 Apr 2013 20:25:37 +0200 (CEST) From: Nicolas Raspail <nicolas@whisperingvault.net> To: FreeBSD-gnats-submit@freebsd.org Subject: ports/177669: nzbget - PostProcess script terminated with unknown status Message-ID: <20130406182537.6DB0156E@shadowland.whisperingvault.net> Resent-Message-ID: <201304061840.r36Ie07p053103@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 177669
>Category: ports
>Synopsis: nzbget - PostProcess script terminated with unknown status
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Sat Apr 06 18:40:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Nicolas Raspail
>Release: FreeBSD 9.0-RELEASE-p3 amd64
>Organization:
>Environment:
System: FreeBSD shadowland.whisperingvault.net 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 root@amd64-bu
ilder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
nzbget 9.1 compiled with the standard gcc compilter from base
>Description:
Even if the PostProcess script is able to do par2 check, unrar extraction and exit with the correct code (93), in the log,
I always see post-process-script for xxx terminated with unknown status. It seems that i386 hosts are not affected by this problem.
>How-To-Repeat:
Install nzgbet and start a download on an amd64 host
>Fix:
Compile the program with an extra option : --enable-sigchld-handler
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130406182537.6DB0156E>