Bug 141206 - [patch] security/amavisd-new: Fix clamd socket name
Summary: [patch] security/amavisd-new: Fix clamd socket name
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Gabor Kovesdan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-05 23:10 UTC by Petr Rehor
Modified: 2009-12-21 22:50 UTC (History)
0 users

See Also:


Attachments
amavisd-new.diff (616 bytes, patch)
2009-12-05 23:10 UTC, Petr Rehor
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Rehor 2009-12-05 23:10:01 UTC
amavisd.conf points to clamd socket /var/run/clamav/clamd but security/clamav port use /var/run/clamav/clamd.sock

How-To-Repeat: Install security/clamav and /var/run/clamav/clamd.
Uncomment clamd section in amavisd.conf.
Run clamd and amavisd.
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2009-12-05 23:10:13 UTC
Responsible Changed
From-To: freebsd-ports-bugs->gabor

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 dfilter service freebsd_committer freebsd_triage 2009-12-21 22:44:27 UTC
gabor       2009-12-21 22:44:13 UTC

  FreeBSD ports repository

  Modified files:
    security/amavisd-new Makefile 
  Log:
  - Match default Clamav socket to the Clamav port's default [1]
  - Change $localhost_name to real hostname instead of 'localhost' [2]
  - Bump PORTREVISION
  
  PR:             ports/141206 [1]
  Submitted by:   Petr Rehor <prehor@gmail.com> [1]
  Requested by:   delphij [2]
  
  Revision  Changes    Path
  1.75      +5 -1      ports/security/amavisd-new/Makefile
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 3 Gabor Kovesdan freebsd_committer freebsd_triage 2009-12-21 22:44:36 UTC
State Changed
From-To: open->closed

I've committed a similar fix for this issue. Thanks for your submission!