Since my last Spamd port update I get this error when I try to start
spamd:
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.
server socket setup failed, retry 1: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server
В Thu, 03 Apr 2014 09:53:10 +0200
Jos Chrispijn пишет:
>Since my last Spamd port update I get this error when I try to start
>spamd:
>spamd not running? (check /var/run/spamd/spamd.pid).
>Starting spamd.
>server socket setup failed, retry 1: spamd: could not create
>IO::So
Hi all.
I'm all about automation. I'd like to automate most tasks so I can
schedule them or write a script with which everything would be done
automatically.
I have some difficulties with current port options framework:
1. Is there a good way to set/unset any option from command line without
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
On Wed, 2 Apr 2014 20:09:45 +0200, Dr. Peter Voigt stated:
> After one of the latest ports tree updates on 10.0-RELEASE I upgraded
> CUPS to version 1.7.1. This version of CUPS reveals some strange
> behavior, although printing itself seems to work as expected.
>
> After the printer has finished
Hi!
> After one of the latest ports tree updates on 10.0-RELEASE I upgraded
> CUPS to version 1.7.1. [...]
One word of warning:
CVE-2014-2707:
http://www.openwall.com/lists/oss-security/2014/04/01/4
--
p...@opsec.eu+49 171 3101372 6 years to go !
__
Sergey V. Dyatko:
use `sockstat -l4 -p783` instead. It show you what user-command-pid
listen that port
USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root perl 1404 5 tcp4 127.0.0.1:783 *:*
root perl 1403 5 tcp4 127.0.0.1:783
Sergey V. Dyatko:
use `sockstat -l4 -p783` instead. It show you what user-command-pid
listen that port
I killed process 1402 and started Spamd. That did the trick, thanks!
I am very curious:
a. why Perl occupied that port.
Tried to retrieve this information from logfiles in /var/log but no
s
On Thu, 03 Apr 2014 14:48:25 +0200
Jos Chrispijn wrote:
>
> Sergey V. Dyatko:
> > use `sockstat -l4 -p783` instead. It show you what user-command-pid
> > listen that port
>
> USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN
> ADDRESS root perl 1404 5 tcp4 127.0.0.
Hi all, postgresql93-server builds fine unless I add krb5 support
(MIT, but doesn't seem to matter). It fails with:
cc -O -pipe -DLDAP_DEPRECATED -Wall -Wmissing-prototypes -Wpointer-arith
-Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute
-Wformat-security -fno-strict-alias
02.04.2014 22:09, Dr. Peter Voigt пишет:
> After one of the latest ports tree updates on 10.0-RELEASE I upgraded
> CUPS to version 1.7.1. This version of CUPS reveals some strange
> behavior, although printing itself seems to work as expected.
>
> After the printer has finished a job the job is st
On 04/03/14 13:57, Jos Chrispijn wrote:
> Sergey V. Dyatko:
>> use `sockstat -l4 -p783` instead. It show you what user-command-pid
>> listen that port
>
> I killed process 1402 and started Spamd. That did the trick, thanks!
>
> I am very curious:
>
> a. why Perl occupied that port.
> Tried to re
On Tue, Apr 1, 2014 at 11:38 AM, Matthew Seaman wrote:
> This is why the quarterly branches exist. 2014Q1 (Just EoL'd) and
> 2014Q2 (just branched from head) will now get only security and port-fix
> type upgrades for the next 3 months. Therefore if your poudriere repo
> had been tracking 2014Q1
On Wed, Apr 2, 2014 at 6:41 AM, Mathieu Arnold wrote:
> +--On 1 avril 2014 11:18:05 -0400 J David wrote:
> | from perl-5.12.3.4_5a to 5.12.3.4_5a1.
>
> Perl 5.12 has been removed about a month and half ago, so, if you were
> still using it, it's going to be a pain, you should upgrade to 5.16.
So
On Thu, 03 Apr 2014 15:49:47 +0100
Matthew Seaman wrote:
> On 04/03/14 13:57, Jos Chrispijn wrote:
> > Sergey V. Dyatko:
> >> use `sockstat -l4 -p783` instead. It show you what user-command-pid
> >> listen that port
> >
> > I killed process 1402 and started Spamd. That did the trick, thanks!
> >
+--On 3 avril 2014 11:05:49 -0400 J David wrote:
| On Wed, Apr 2, 2014 at 6:41 AM, Mathieu Arnold wrote:
|> +--On 1 avril 2014 11:18:05 -0400 J David
|> wrote:
|> | from perl-5.12.3.4_5a to 5.12.3.4_5a1.
|>
|> Perl 5.12 has been removed about a month and half ago, so, if you were
|> still using
Am Thu, 03 Apr 2014 18:32:32 +0400
schrieb Boris Samorodov :
> I've got a diff to update print/cups-filters from version 1.0.42
> to version 1.0.50. Please, dive it a try. It may help. (This patch
> may not be committed as is since it does not build at 8.x due to
> incomplete network headers).
>
If your ports tree is managed by subversion, you can just selectively
update foobar's directory. As long as it doesn't depend on a specific
version of perl, poudriere will see that it is updated and perl is
not.
On Thu, Apr 3, 2014 at 10:36 AM, Mathieu Arnold wrote:
> +--On 3 avril 2014 11:05:49
03.04.2014 20:10, Dr. Peter Voigt пишет:
> Am Thu, 03 Apr 2014 18:32:32 +0400
> schrieb Boris Samorodov :
>
>> I've got a diff to update print/cups-filters from version 1.0.42
>> to version 1.0.50. Please, dive it a try. It may help. (This patch
>> may not be committed as is since it does not buil
On Thu, Apr 3, 2014 at 11:36 AM, Mathieu Arnold wrote:
> Something built for perl 5.14.0 will work with perl 5.14.5.a6_7.
This is one of those things that's true most of the time. And on
those occasions when it isn't, the fallout is spectacular. It does
not come up more often because poudriere
Thank you for the informative responses - I learned a lot.
Best regards.
Jos Chrispijn:
Since my last Spamd port update I get this error when I try to start
spamd:
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.
On 4/3/2014 19:52, J David wrote:
>
> The net effect of all of this is that even if you do take 24 hours and
> rebuild all the ports that depend on perl because of that foobar
> vulnerability, including bazqux, you *still* end up pissing off the
> bazqux users because it rev'd bazqux from 1.5 to 2
On 04/04/2014 05:13, Jos Chrispijn wrote:
>Since my last Spamd port update I get this error when I try to start
>spamd:
>spamd not running? (check /var/run/spamd/spamd.pid).
>Starting spamd.
For SpamAssassin, you need to provide the pidfile specification in
/etc/rc.conf.
mta4# g
On Fri, 04 Apr 2014 06:57:29 +1100
John Marshall wrote:
> On 04/04/2014 05:13, Jos Chrispijn wrote:
> >Since my last Spamd port update I get this error when I try to
> > start spamd:
> >spamd not running? (check /var/run/spamd/spamd.pid).
> >Starting spamd.
>
> For SpamAssassin, you n
+--On 3 avril 2014 21:54:52 +0200 John Marino
wrote:
| I don't think anybody is going to reprogram the logic of poudriere
| though. This is just an academic discussion of what could be done, but
| I doubt anybody wants to actually implement it due to the potential side
| effects (and the (limited
On 04/04/2014 09:26, RW wrote:
> On Fri, 04 Apr 2014 06:57:29 +1100
> John Marshall wrote:
>> For SpamAssassin, you need to provide the pidfile specification in
>> /etc/rc.conf.
>>
>> mta4# grep pidfile /etc/rc.conf
>> spamd_pidfile="/var/run/spamd/spamd.pid"
>
>
> That's already the default.
Hi,
I have a patch to fix the "Failed to parse/validate config: Failed to
init Log options" problem whenever I start Tor on FreeBSD. It is:
--- Makefile.old2014-04-03 19:48:25.0 -0400
+++ Makefile2014-04-03 19:49:57.0 -0400
@@ -42,6 +42,9 @@
CONFLICTS= tor-deve
Hi,
I have a patch to fix the "Failed to parse/validate config: Failed to
init Log options" problem whenever I start Tor on FreeBSD. It is:
--- Makefile.old2014-04-03 19:48:25.0 -0400
+++ Makefile2014-04-03 19:49:57.0 -0400
@@ -42,6 +42,9 @@
CONFLICTS= tor-deve
Hi,
Sorry for the duplicate email.
-Neel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On Thu, Apr 03, 2014 at 09:53:10AM +0200, Jos Chrispijn wrote:
>Since my last Spamd port update I get this error when I try to start
Same here, I've had this happen every time when I update spamassassin,
using portmaster, which is using pkgng.
This was taken after I had updated spamassassin
On Fri, Apr 04, 2014 at 08:52:29AM +0300 I heard the voice of
Esa Karkkainen, and lo! it spake thus:
> On Thu, Apr 03, 2014 at 09:53:10AM +0200, Jos Chrispijn wrote:
> >Since my last Spamd port update I get this error when I try to start
>
> Same here, I've had this happen every time when I up
31 matches
Mail list logo
