From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 83dfa1d7b2e5946a9405a27dba9b3a81d958baee
Date: Sun, 29 Sep 2013 22:26:57 +0200 [thread overview]
Message-ID: <20130929202657.6DF9A207B0@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
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, fifteen has been updated
via 83dfa1d7b2e5946a9405a27dba9b3a81d958baee (commit)
from 26b34186b3788b9ee58246e5b09748ea7b6df6b3 (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 83dfa1d7b2e5946a9405a27dba9b3a81d958baee
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Sun Sep 29 22:26:14 2013 +0200
clamav: disable PaX mprotect for freshclam.
-----------------------------------------------------------------------
Summary of changes:
lfs/clamav | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/clamav b/lfs/clamav
index aa225f4..51febd9 100644
--- a/lfs/clamav
+++ b/lfs/clamav
@@ -94,8 +94,9 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
mkdir -p /var/run/clamav
chown clamav:clamav /var/run/clamav
- # Disable PaX mprotect for clamd
+ # Disable PaX mprotect for clamd and freshclam
paxctl -cm /usr/sbin/clamd
+ paxctl -cm /usr/bin/freshclam
@rm -rf $(DIR_APP)
@$(POSTBUILD)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-09-29 20:26 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=20130929202657.6DF9A207B0@argus.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