From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. d451f131ff19cc090d78712adc9309dd5bed2990
Date: Thu, 16 Oct 2025 16:42:12 +0000 (UTC) [thread overview]
Message-ID: <4cnYdc2rfgz2xhX@people01.haj.ipfire.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via d451f131ff19cc090d78712adc9309dd5bed2990 (commit)
from f1e4331fa76b628c91057aca8e501c87de90283b (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit d451f131ff19cc090d78712adc9309dd5bed2990
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Thu Oct 16 18:40:08 2025 +0200
general-functions.pl: Read output first before we wait for the process to terminate
When generating IPS reports, the reporter could not write to the output,
therefore blocked and the CGI script timed out.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/cfgroot/general-functions.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/cfgroot/general-functions.pl b/config/cfgroot/general-functions.pl
index 94d0e7440..1c3374d86 100644
--- a/config/cfgroot/general-functions.pl
+++ b/config/cfgroot/general-functions.pl
@@ -66,13 +66,13 @@ sub system_output($) {
die "Could not execute @command: $!";
}
- waitpid($pid, 0);
-
while (<OUTPUT>) {
push(@output, $_);
}
close(OUTPUT);
+ waitpid($pid, 0);
+
return @output;
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-10-16 16:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4cnYdc2rfgz2xhX@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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