Spamd

[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::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 2: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 3: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 4: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 5: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 6: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 7: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 8: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 9: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783:
   Address already in use
   ./sa-spamd: WARNING: failed to start spamd
   SpamAssassin version 3.4.0
 running on Perl version 5.16.3
   nmap -v localhost:
   Starting Nmap 6.40 ( [1]http://nmap.org ) at 2014-04-03 09:44 CEST
   Initiating SYN Stealth Scan at 09:44
   Scanning localhost (127.0.0.1) [1000 ports]
   Discovered open port 25/tcp on 127.0.0.1
   Discovered open port 587/tcp on 127.0.0.1
   Discovered open port 993/tcp on 127.0.0.1
   Discovered open port 995/tcp on 127.0.0.1
   Increasing send delay for 127.0.0.1 from 0 to 5 due to 11 out of 21
   dropped probes since last increase.
   Discovered open port 143/tcp on 127.0.0.1
   Discovered open port 3306/tcp on 127.0.0.1
   Discovered open port 110/tcp on 127.0.0.1
   >> Discovered open port 783/tcp on 127.0.0.1 <<
   Increasing send delay for 127.0.0.1 from 5 to 10 due to 43 out of 142
   dropped probes since last increase.
   Increasing send delay for 127.0.0.1 from 10 to 20 due to
   max_successful_tryno increase to 4
   --- cut ---
   /letc/services file no port 783 reserved:
   multiling-http  777/tcp#Multiling HTTP
   multiling-http  777/udp#Multiling HTTP
   wpgs780/tcp
   wpgs780/udp
   mdbs_daemon 800/tcp
   mdbs_daemon 800/udp
   Can you tell me if this is a ports issue or how I could solve this?
   Thanks!
   Jos

References

   1. http://nmap.org/
___
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"

Re: Spamd

[Sergey V. Dyatko]

В 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::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 2: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 3: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 4: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 5: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 6: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 7: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 8: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>server socket setup failed, retry 9: spamd: could not create
>IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
>spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783:
>Address already in use
>./sa-spamd: WARNING: failed to start spamd
>SpamAssassin version 3.4.0
>  running on Perl version 5.16.3
>nmap -v localhost:

use `sockstat -l4 -p783` instead.
It show you what user-command-pid listen that port 

>Starting Nmap 6.40 ( [1]http://nmap.org ) at 2014-04-03 09:44 CEST
>Initiating SYN Stealth Scan at 09:44
>Scanning localhost (127.0.0.1) [1000 ports]
>Discovered open port 25/tcp on 127.0.0.1
>Discovered open port 587/tcp on 127.0.0.1
>Discovered open port 993/tcp on 127.0.0.1
>Discovered open port 995/tcp on 127.0.0.1
>Increasing send delay for 127.0.0.1 from 0 to 5 due to 11 out of 21
>dropped probes since last increase.
>Discovered open port 143/tcp on 127.0.0.1
>Discovered open port 3306/tcp on 127.0.0.1
>Discovered open port 110/tcp on 127.0.0.1
>>> Discovered open port 783/tcp on 127.0.0.1 <<
>Increasing send delay for 127.0.0.1 from 5 to 10 due to 43 out of 142
>dropped probes since last increase.
>Increasing send delay for 127.0.0.1 from 10 to 20 due to
>max_successful_tryno increase to 4
>--- cut ---
>/letc/services file no port 783 reserved:
>multiling-http  777/tcp#Multiling HTTP
>multiling-http  777/udp#Multiling HTTP
>wpgs780/tcp
>wpgs780/udp
>mdbs_daemon 800/tcp
>mdbs_daemon 800/udp
>Can you tell me if this is a ports issue or how I could solve this?
>Thanks!
>Jos
> 
> References
> 
>1. http://nmap.org/
> ___
> 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"




--
wbr, tiger

___
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"

working with port options from commandline

[Volodymyr Kostyrko]

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 
firing up dialog? Something like 'make -C port/dir -DSET=OPT1,OPT2 
-DUNSET=OPT3 updateconfig'.


2. Is there a good way to query for option updates? You know when you 
are building a port the option dialog will still be shown if there are 
new options not present in current config. Can I get those options 
somehow like 'make -C port/dir changedconfig'?


I think I need to write some scripts to handle this situations myself 
but I just want to ask whether someone had done that before or maybe 
such functionality is pending?


--
Sphinx of black quartz, judge my vow.
___
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"

FreeBSD ports you maintain which are out of date

[portscout]

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 can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
japanese/jishyo | 0.1 | 0.2
+-+
japanese/skk-jisyo  | 201302  | 201404
+-+
japanese/skk-jisyo-cdb  | 201302  | 201404
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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"

Re: Problems after upgrade to CUPS 1.7.1 - gstoraster error

[Jerry]

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 a job the job is still being marked as
> active. The CUPS web interface has marked the job as 'stopped 
> "Filter failed"' and the CUPS version of "lpq" still lists the job as
> being queued.
> 
> The cups log file is directed on my system to rsyslogd and shows
> following error messages:
> 
> - Job stopped due to filter errors; please consult the error_log file
>   for details.
> - /usr/local/libexec/cups/filter/gstoraster) stopped with status 1.
> 
> Fortunately these errors do not block the printing system, e.g. I can
> start further print jobs which will be printed immediately. However it
> is annoying that the printing queue gets filled more and more.
> 
> Here are my installed CUPS related packages:
> 
> # pkg version -v |grep cups
> cups-1.7.1 =   up-to-date with port
> cups-base-1.7.1=   up-to-date with port
> cups-client-1.7.1  =   up-to-date with portIn 
> cups-filters-1.0.42=   up-to-date with port
> cups-image-1.7.1   =   up-to-date with port
> cups-pstoraster-8.15.4_7   =   up-to-date with port
> gutenprint-cups-5.2.8_1=   up-to-date with port
> 
> Any advice is appreciated.
> 
> Regards,
> Peter

In the past when I have experienced problems with CUPS, I found it far
easier to go to the source; ie report the problem directly to the CUPS
developers. The CUPS forum is quite helpful and you would probably be
better served by utilizing their services. I assume you are not a member.
You can subscribe here: .

-- 
Jerry


___
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"

Re: Problems after upgrade to CUPS 1.7.1 - gstoraster error

[Kurt Jaeger]

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 !
___
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"

Re: Spamd

[Jos Chrispijn]

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 *:*
root perl   1402  5  tcp4   127.0.0.1:783 *:*

Is this Perl itself or is this a program that uses Perl for this port?

wbr, Jos


___
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"

Re: Spamd

[Jos Chrispijn]

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 
success. May that be an inward traffic issue on port 783 that triggered 
Perl and kept it occupied for Spamd?


b. Is it unsafe or possible to let spamd use another port if 783 is 
occupied. May that be a security risk?


T|hanks for your help,
Jos Chrispijn


___
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"

Re: Spamd

[RW]

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.1:783 *:*
> root perl   1403  5  tcp4   127.0.0.1:783 *:*
> root perl   1402  5  tcp4   127.0.0.1:783 *:*
> 
> Is this Perl itself or is this a program that uses Perl for this port?

It'll be  the spamassassin master process and default of two children.

By the look of it the rc.d script couldn't find a spamassassin perl
process that matched the PID in the pid file so couldn't shut the old
version down before starting the new. This is commonly because the pid
file isn't writeable, but using port 783 implies that it started as
root.

Check that the current pid file contains a correct value.  
___
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"

postgresql-server fails with krb5 support

[Gareth de Vaux]

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-aliasing -fwrapv initdb.o findtimezone.o 
localtime.o encnames.o  -L../../../src/port -L../../../src/common 
-L/usr/local/lib -Wl,-rpath,/usr/lib:/usr/local/lib -L/usr/local/lib 
-L/usr/local/lib -L/usr/local/lib  -L/usr/local/lib -Wl,--as-needed 
-Wl,-R'/usr/local/lib'  -lpgport -lpgcommon -lxml2 -lssl -lcrypto -lkrb5 
-lcom_err -lz -lreadline -lcrypt -lm  -o initdb
initdb.o: In function `check_authmethod_unspecified':
initdb.c:(.text+0x27): undefined reference to `libintl_gettext'
initdb.o: In function `warn_on_mount_point':
initdb.c:(.text+0x4f): undefined reference to `libintl_gettext'
initdb.c:(.text+0x7b): undefined reference to `libintl_gettext'
initdb.c:(.text+0x99): undefined reference to `libintl_gettext'
initdb.o: In function `check_authmethod_valid':
initdb.c:(.text+0x130): undefined reference to `libintl_gettext'

etc

-lintl gets dropped from the compile line when -lkrb5 is added for some reason.


$ uname -a
FreeBSD imap1 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0: Thu Aug 16 13:53:45 
SAST 2012 root@imap1:/usr/obj/usr/src/sys/GENERIC  amd64
___
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"

Re: Problems after upgrade to CUPS 1.7.1 - gstoraster error

[Boris Samorodov]

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 still being marked as
> active. The CUPS web interface has marked the job as 'stopped 
> "Filter failed"' and the CUPS version of "lpq" still lists the job as
> being queued.
> 
> The cups log file is directed on my system to rsyslogd and shows
> following error messages:
> 
> - Job stopped due to filter errors; please consult the error_log file
>   for details.
> - /usr/local/libexec/cups/filter/gstoraster) stopped with status 1.
> 
> Fortunately these errors do not block the printing system, e.g. I can
> start further print jobs which will be printed immediately. However it
> is annoying that the printing queue gets filled more and more.
> 
> Here are my installed CUPS related packages:
> 
> # pkg version -v |grep cups
> cups-1.7.1 =   up-to-date with port
> cups-base-1.7.1=   up-to-date with port
> cups-client-1.7.1  =   up-to-date with port
> cups-filters-1.0.42=   up-to-date with port
> cups-image-1.7.1   =   up-to-date with port
> cups-pstoraster-8.15.4_7   =   up-to-date with port
> gutenprint-cups-5.2.8_1=   up-to-date with port
> 
> Any advice is appreciated.

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 that do not help, then try to enable debug (set "LogLevel debug"
at cupsd.conf) and look at logs (/var/log/cups/error_log in particular)
for any errors.

Patch is included.
-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
Index: Makefile
===
--- Makefile(revision 349924)
+++ Makefile(working copy)
@@ -1,7 +1,7 @@
 # $FreeBSD$
 
 PORTNAME=  cups-filters
-PORTVERSION=   1.0.42
+PORTVERSION=   1.0.50
 CATEGORIES=print
 MASTER_SITES=  http://www.openprinting.org/download/cups-filters/
 
@@ -20,7 +20,8 @@
libfontconfig.so:${PORTSDIR}/x11-fonts/fontconfig \
libpoppler.so:${PORTSDIR}/graphics/poppler
 
-USES=  compiler:c++11-lib pathfix pkgconfig tar:xz
+USES=  compiler:c++11-lib pathfix pkgconfig shebangfix tar:xz
+SHEBANG_FILES= filter/textonly
 USE_GNOME= glib20
 USE_GHOSTSCRIPT=   yes
 GNU_CONFIGURE= yes
@@ -45,5 +46,7 @@
 post-install:
@${RM} -rf ${STAGEDIR}${PREFIX}/libexec/cups/filter/foomatic-rip \
${STAGEDIR}${PREFIX}/man/man1/foomatic-rip.1
+   @${STRIP_CMD} ${STAGEDIR}${PREFIX}/lib/libcupsfilters.so.1 \
+   ${STAGEDIR}${PREFIX}/lib/libfontembed.so.1
 
 .include 
Index: distinfo
===
--- distinfo(revision 349924)
+++ distinfo(working copy)
@@ -1,2 +1,2 @@
-SHA256 (cups-filters-1.0.42.tar.xz) = 
3df524207ab24472430cffba7f01407b8adc094ec40094c5f6682d5a88a70dd6
-SIZE (cups-filters-1.0.42.tar.xz) = 1097860
+SHA256 (cups-filters-1.0.50.tar.xz) = 
771bdaeaa171cfb3850b229d5d167bde2abcd40b900075ae72d4867acc8adbe7
+SIZE (cups-filters-1.0.50.tar.xz) = 1309912
Index: pkg-plist
===
--- pkg-plist   (revision 349924)
+++ pkg-plist   (working copy)
@@ -48,6 +48,7 @@
 sbin/cups-browsed
 share/cups/banners/classified
 share/cups/banners/confidential
+share/cups/banners/form
 share/cups/banners/secret
 share/cups/banners/standard
 share/cups/banners/topsecret
@@ -57,6 +58,10 @@
 share/cups/charsets/pdf.utf-8.simple
 share/cups/data/default-testpage.pdf
 share/cups/data/default.pdf
+share/cups/data/form_english.pdf
+share/cups/data/form_english_in.odt
+share/cups/data/form_russian.pdf
+share/cups/data/form_russian_in.odt
 share/cups/data/testprint
 share/cups/drv/cupsfilters.drv
 share/cups/mime/cupsfilters.convs
@@ -68,6 +73,7 @@
 %%PORTDOCSDOCSDIR%%/INSTALL
 %%PORTDOCSDOCSDIR%%/NEWS
 %%PORTDOCSDOCSDIR%%/README
+share/ppd/cupsfilters/Fuji_Xerox-DocuPrint_CM305_df-PDF.ppd
 share/ppd/cupsfilters/Generic-PDF_Printer-PDF.ppd
 share/ppd/cupsfilters/HP-Color_LaserJet_CM3530_MFP-PDF.ppd
 share/ppd/cupsfilters/HP-PhotoSmart_Pro_B8300-hpijs-pdftoijs.ppd
___
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"

Re: Spamd

[Matthew Seaman]

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 retrieve this information from logfiles in /var/log but no
> success. May that be an inward traffic issue on port 783 that triggered
> Perl and kept it occupied for Spamd?
> 
> b. Is it unsafe or possible to let spamd use another port if 783 is
> occupied. May that be a security risk?

Assuming 'spamd' here is part of spamassassin then it is a daemon
written in perl, and the command name will show up as perl in sockstat
listings.

In my experience, it is quite common for this daemon to end up running
under a different PID than the one recorded under /var/run -- so the
system initialization scripts 'sa-spamd' think it isn't running, and
then you get the fight over access to port 783 the OP saw.  Killing the
processes using port 783 and restarting spamd should work.

The situation is complicated by the /other/ spamd -- which is an OpenBSD
thing which works via pf to implement greylisting, teergrube and various
other anti-spam things.  Meaning the SpamAssassin 'sa-spamd' startup
script can't simply kill anything called spamd.

Cheers,

Matthew




signature.asc
Description: OpenPGP digital signature

Re: Updating less-than-everything with poudriere & pkgng

[J David]

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 it would probably not have had those perl
> updates to deal with, but it would have had foobar-1.2.3 security fixes.
>
> Of course, right about now, you get to have an upgrade frenzy applying 3
> months worth of changes in one fell swoop, as there's the switchover
> from 2014Q1 to 2014Q2 happening right now.

That seems like a step in the right direction, though it won't work
for us.  The requirements for us are to support an environment with
security updates for at least a year; it sounds like these ports
branches are completely abandoned after three months, receiving no
further security updates no matter how critical.  Maybe in the future
somebody will volunteer to maintain "LTS" branches of the ports tree.

> There's no way I know of to use poudriere to selectively update just
> packages from the dependency tree involving foobar but not ones
> involving perl.

That's unfortunate. :(  All we need to do is find a way to skip the
"delete outdated packages" step that doesn't also skip the "delete
packages with missing dependencies step."  Then we could just remove
foobar and rebuild.  Is that feasible to do?  If so, where in the
poudriere code would we look?

> About the only way I can think of to achieve that is to
> apply selective updates to your ports tree that you have checked out of
> SVN, which is a pain in the posterior and not always guarranteed to work
> properly.

It sounds like this may be our only other option.

Thanks!
___
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"

Re: Updating less-than-everything with poudriere & pkgng

[J David]

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.

Sorry, the version numbers 1.2.3 and 12.3.4_5 were chosen as examples,
not meant to be taken literally.

> Sure, instead of using bulk -a or bulk -f portlist, just use bulk
> category/foobar, it'll rebuild only the package you asked for, and its
> dependencies.

This will cause disaster.  If you do this to rebuild foobar, poudriere
will also update perl.  Then, when you install the fixed foobar, pkg
will intall the updated perl.  Then the unrelated package bazqux you
didn't rebuild but which also depends on perl and isn't compatible
with the new version silently breaks.  And the first you will hear
about it is when all the bazqux users from the third floor show up at
the door to your office with torches and pitchforks.

What we are looking to do is rebuild only foobar and the things that
depend on foobar, NOT the things that foobar depends on.

Thanks!
___
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"

Re: Spamd

[RW]

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!
> > 
> > I am very curious:
> > 
> > a. why Perl occupied that port.
> > Tried to retrieve this information from logfiles in /var/log but no
> > success. May that be an inward traffic issue on port 783 that
> > triggered Perl and kept it occupied for Spamd?
> > 
> > b. Is it unsafe or possible to let spamd use another port if 783 is
> > occupied. May that be a security risk?
> 
> Assuming 'spamd' here is part of spamassassin then it is a daemon
> written in perl, and the command name will show up as perl in sockstat
> listings.
> 
> In my experience, it is quite common for this daemon to end up running
> under a different PID than the one recorded under /var/run -- so the
> system initialization scripts 'sa-spamd' think it isn't running, and
> then you get the fight over access to port 783 the OP saw.  Killing
> the processes using port 783 and restarting spamd should work.
> 
> The situation is complicated by the /other/ spamd -- which is an
> OpenBSD thing which works via pf to implement greylisting, teergrube
> and various other anti-spam things.  Meaning the SpamAssassin
> 'sa-spamd' startup script can't simply kill anything called spamd.

Support for pid files is built into rcng and used a combination of pid
and name, sa-spamd uses this and correctly passes the expected pid
file path to spamd. 

In my experience it does normally work, unless spamd is started as an
unprivileged user via the spamd_user variable in rc.conf, rather
dropping privileges - that's not happening here because the existing
process used port 783.
___
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"

Re: Updating less-than-everything with poudriere & pkgng

[Mathieu Arnold]

+--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 it, it's going to be a pain, you should upgrade to 5.16.
| 
| Sorry, the version numbers 1.2.3 and 12.3.4_5 were chosen as examples,
| not meant to be taken literally.

Well, yes, just making sure :-)

|> Sure, instead of using bulk -a or bulk -f portlist, just use bulk
|> category/foobar, it'll rebuild only the package you asked for, and its
|> dependencies.
| 
| This will cause disaster.  If you do this to rebuild foobar, poudriere
| will also update perl.  Then, when you install the fixed foobar, pkg
| will intall the updated perl.  Then the unrelated package bazqux you
| didn't rebuild but which also depends on perl and isn't compatible
| with the new version silently breaks.  And the first you will hear
| about it is when all the bazqux users from the third floor show up at
| the door to your office with torches and pitchforks.
| 
| What we are looking to do is rebuild only foobar and the things that
| depend on foobar, NOT the things that foobar depends on.

Poudriere only rebuilds things to be on the safe side.
Something built for perl 5.14.0 will work with perl 5.14.5.a6_7. If a port
that needs Perl has changes introduced from the Perl update, it will get a
portrevision bump.
If pkg detects that a shared library was updated, it will also force the
upgrade of the depending ports.

-- 
Mathieu Arnold
___
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"

Re: Problems after upgrade to CUPS 1.7.1 - gstoraster error

[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 build at 8.x due to
> incomplete network headers).
> 
> If that do not help, then try to enable debug (set "LogLevel debug"
> at cupsd.conf) and look at logs (/var/log/cups/error_log in
> particular) for any errors.
> 
> Patch is included.

Thanks for all advices so far.

I would like to give this patch a try but I am worrying about possibly
confusing pkg(ng) in case of having to downgrade again.

If I got you right, Boris, your patch should upgrade print/cups-filters
to version 1.0.50. If I have the need to downgrade again, I will use
the original Makefile. Can I build and install the original version
1.0.42 again without confusing pkg(ng)?

I ask because I am rather new to FreeBSD and right after having learned
old pkg administration I am still in the process of understanding
pkg(ng). I have learned from the forum and from own bad experiences that
the package database can easily be mangled leaving you with a lot of
work to get things running again.

I should mention that my latest attempt of increasing the log level to
"debug" did not reveal any additional helpful information - if I
remember correctly :-)

Regards,
Peter
___
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"

Re: Updating less-than-everything with poudriere & pkgng

[Reed A. Cartwright]

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 -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 it, it's going to be a pain, you should upgrade to 5.16.
> |
> | Sorry, the version numbers 1.2.3 and 12.3.4_5 were chosen as examples,
> | not meant to be taken literally.
>
> Well, yes, just making sure :-)
>
> |> Sure, instead of using bulk -a or bulk -f portlist, just use bulk
> |> category/foobar, it'll rebuild only the package you asked for, and its
> |> dependencies.
> |
> | This will cause disaster.  If you do this to rebuild foobar, poudriere
> | will also update perl.  Then, when you install the fixed foobar, pkg
> | will intall the updated perl.  Then the unrelated package bazqux you
> | didn't rebuild but which also depends on perl and isn't compatible
> | with the new version silently breaks.  And the first you will hear
> | about it is when all the bazqux users from the third floor show up at
> | the door to your office with torches and pitchforks.
> |
> | What we are looking to do is rebuild only foobar and the things that
> | depend on foobar, NOT the things that foobar depends on.
>
> Poudriere only rebuilds things to be on the safe side.
> Something built for perl 5.14.0 will work with perl 5.14.5.a6_7. If a port
> that needs Perl has changes introduced from the Perl update, it will get a
> portrevision bump.
> If pkg detects that a shared library was updated, it will also force the
> upgrade of the depending ports.
>
> --
> Mathieu Arnold
> ___
> 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"



-- 
Reed A. Cartwright, PhD
Assistant Professor of Genomics, Evolution, and Bioinformatics
School of Life Sciences
Center for Evolutionary Medicine and Informatics
The Biodesign Institute
Arizona State University
==
Address: The Biodesign Institute, PO Box 875301, Tempe, AZ 85287-5301 USA
Packages: The Biodesign Institute, 1001 S. McAllister Ave, Tempe, AZ
85287-5301 USA
Office: Biodesign A-224A, 1-480-965-9949
Website: http://cartwrig.ht/
___
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"

Re: Problems after upgrade to CUPS 1.7.1 - gstoraster error

[Boris Samorodov]

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 build at 8.x due to
>> incomplete network headers).
>>
>> If that do not help, then try to enable debug (set "LogLevel debug"
>> at cupsd.conf) and look at logs (/var/log/cups/error_log in
>> particular) for any errors.
>>
>> Patch is included.
> 
> Thanks for all advices so far.
> 
> I would like to give this patch a try but I am worrying about possibly
> confusing pkg(ng) in case of having to downgrade again.
> 
> If I got you right, Boris, your patch should upgrade print/cups-filters
> to version 1.0.50.

Yes.

> If I have the need to downgrade again, I will use
> the original Makefile.

The patch changes three files. So you may restore them all.
You may use PATCH(1) with -R option to restore status quo.

> Can I build and install the original version
> 1.0.42 again without confusing pkg(ng)?

I use just delete an old package and then build and install a new one
using the portstree. Should be OK to use vice versa (from a new version
to an old one).

> I ask because I am rather new to FreeBSD and right after having learned
> old pkg administration I am still in the process of understanding
> pkg(ng). I have learned from the forum and from own bad experiences that
> the package database can easily be mangled leaving you with a lot of
> work to get things running again.

Well, for _me_ playing with _one_ port (not touching any dependencies)
was always a success.

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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"

Re: Updating less-than-everything with poudriere & pkgng

[J David]

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 does such a good job
protecting against it by ensuring that whatever depends on perl is
also rebuilt whenever perl changes.  What we are trying to do is stop
perl from being rebuilt just because we are building something way
down the line that depends on it.

> If a port
> that needs Perl has changes introduced from the Perl update, it will get a
> portrevision bump.

This problem is more about the opposite case, where Perl changes out
from under a port that uses it.  Perl got singled out as my example
simply because when speaking about the FreeBSD "ports tree" it is the
closest thing there is to a root.

Another example would be apr.  Apache has a security issue -> rebuild
apache -> poudriere builds a new version of apr -> apr revs its shared
library version -> deploy fix -> unrelated port subversion (not
rebuilt) abruptly quits working -> torches and pitchforks.  Of course
in that case it's not as big a deal because there aren't tens of
thousands of ports that depend on apr so, provided you realize apr is
getting updated, you can probably find them.  Which is fine.  Unless
the new version of subversion has compatibility issues of its own your
developer team isn't ready to deal with.  All because Apache has a
segfault when logging truncating cookies.

Although there's not a "build this, and it's dependents, and it's
dependencies' dependents" option either, so you are still pretty much
stuck building everything if you want to make sure you found them all.

Then again, Apache also depends on perl...

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.0 and 2.0 isn't
backward compatible.  And the people using bazqux don't take "well
foobar had a security issue" as a reason for disrupting them, because
they don't care one whit about foobar.

It's definitely a rock-and-hardplace situation.  It's not clear that
an ideal answer even exists, but it would be nice to get a little bit
closer.

Thanks!
___
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"

Re: Spamd

[Jos Chrispijn]

   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.
___
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"

Re: Updating less-than-everything with poudriere & pkgng

[John Marino]

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.0 and 2.0 isn't
> backward compatible.  And the people using bazqux don't take "well
> foobar had a security issue" as a reason for disrupting them, because
> they don't care one whit about foobar.

You've been throwing out this 8000 packages = 24 hours bit for a couple
of days now.  Our setup builds packages at an average rate of 600
packages an hour, ranging from 100 to 1600 pkg/hour impulse, and that is
counting the monster-size packages.

If you are really serious about all these requirements, get a better
build machine.  You could probably build 8000 packages with a single
machine in 10 hours or less depending on the actual packages (e.g. if
they are mostly perl packages it could be faster)

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) gain vs the implementation cost).

John
___
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"

Re: Spamd

[John Marshall]

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# grep pidfile /etc/rc.conf
  spamd_pidfile="/var/run/spamd/spamd.pid"

-- 
John Marshall



signature.asc
Description: OpenPGP digital signature

Re: Spamd

[RW]

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 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.
___
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"

Re: Updating less-than-everything with poudriere & pkgng

[Mathieu Arnold]

+--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) gain vs the implementation cost).

Yay, we've talked about this quite a lot, and there's the simple and always
working way, but maybe somewhat overkill sometime, that poudriere is doing
right now, and there is the way that *always* gets out *exactly* *right*
what package to rebuild, and what package not to rebuild.  That second way
of doing things would be a monsterously beast of bugridden code, and take
so much reverse engineering into each package to figure out what it needs
it would certainly take more time in the end.

-- 
Mathieu Arnold
___
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"

Re: Spamd

[John Marshall]

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.

Hmmm. So it is, and all still works fine when I remove spamd_pidfile
from rc.conf. I wonder why I did that? My recollection was that I had
done that many years ago to fix a problem like the OP's. Sorry for the
noise.

-- 
John Marshall



signature.asc
Description: OpenPGP digital signature

[patch] - Fix for "Failed to parse/validate config: Failed to init Log options"

[Neel Chauhan]

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-devel-[0-9]*

+PLIST_SUB= USERS=${USERS}
+PLIST_SUB+=GROUPS=${GROUPS}
+
 .include 

 .if ( (${OSVERSION} < 90) || \

--- pkg-plist.old   2014-04-03 19:37:16.0 -0400
+++ pkg-plist   2014-04-03 19:47:56.0 -0400
@@ -8,6 +8,8 @@
 man/man1/tor-resolve.1.gz
 man/man1/tor.1.gz
 man/man1/torify.1.gz
+@exec touch /var/log/tor ; chown %%USERS%%:%%GROUPS%% /var/log/tor
+@exec mkdir /var/run/tor ; chown -R %%USERS%%:%%GROUPS%% /var/run/tor
 %%DATADIR%%/geoip
 %%DATADIR%%/geoip6
 @dirrm %%DATADIR%%

I'm in a hurry to post this because I'm a high school student and I 
don't want my mom to be too angry with me, but I did test this and it 
worked. And my Postfix server couldn't send this email the first time (I 
actually run my own email server, and from home!). But anyways, hope you 
enjoy it.

-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"

[patch] - Fix for "Failed to parse/validate config: Failed to init Log options"

[Neel Chauhan]

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-devel-[0-9]*

+PLIST_SUB= USERS=${USERS}
+PLIST_SUB+=GROUPS=${GROUPS}
+
 .include 

 .if ( (${OSVERSION} < 90) || \

--- pkg-plist.old   2014-04-03 19:37:16.0 -0400
+++ pkg-plist   2014-04-03 19:47:56.0 -0400
@@ -8,6 +8,8 @@
 man/man1/tor-resolve.1.gz
 man/man1/tor.1.gz
 man/man1/torify.1.gz
+@exec touch /var/log/tor ; chown %%USERS%%:%%GROUPS%% /var/log/tor
+@exec mkdir /var/run/tor ; chown -R %%USERS%%:%%GROUPS%% /var/run/tor
 %%DATADIR%%/geoip
 %%DATADIR%%/geoip6
 @dirrm %%DATADIR%%

I'm in a hurry to post this because I'm a high school student and I 
don't want my mom to be too angry with me, but I did test this and it 
worked. Hope you enjoy it.

-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"

Re: [patch] - Fix for "Failed to parse/validate config: Failed to init Log options"

[Neel Chauhan]

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"

Re: Spamd

[Esa Karkkainen]

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

# /usr/local/etc/rc.d/sa-spamd status
spamd is not running.
# /usr/local/etc/rc.d/sa-spamd start
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 socket setup failed, retry 2: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 3: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 4: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
^C
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   988   5  tcp4   127.0.0.1:783 *:*
root perl   987   5  tcp4   127.0.0.1:783 *:*
root perl   986   5  tcp4   127.0.0.1:783 *:*
# kill 986
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
# /usr/local/etc/rc.d/sa-spamd start
Starting spamd.
# /usr/local/etc/rc.d/sa-spamd status
spamd is running as pid 57023.
# portmaster spamassassin-3.4.0_9

[ building of spamassassin-3.4.0_9 removed ]

===>>> Re-installation of spamassassin-3.4.0_9 complete

===>>> Exiting
# /usr/local/etc/rc.d/sa-spamd status
spamd is not running.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   57025 5  tcp4   127.0.0.1:783 *:*
root perl   57024 5  tcp4   127.0.0.1:783 *:*
root perl   57023 5  tcp4   127.0.0.1:783 *:*
# ls -l /var/run/spamd/spamd.pid
ls: /var/run/spamd/spamd.pid: No such file or directory
# printf '57023' > /var/run/spamd/spamd.pid
# /usr/local/etc/rc.d/sa-spamd status
spamd is running as pid 57023.
# /usr/local/etc/rc.d/sa-spamd restart
Stopping spamd.
Waiting for PIDS: 57023.
Starting spamd.
# /usr/local/etc/rc.d/sa-spamd status
spamd is running as pid 66760.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   66762 5  tcp4   127.0.0.1:783 *:*
root perl   66761 5  tcp4   127.0.0.1:783 *:*
root perl   66760 5  tcp4   127.0.0.1:783 *:*

So IMHO either portmaster or pkgng just removes the spamd.pid file, and
in reality does not stop spamd.

# grep HANDLE_RC_SCRIPTS /usr/local/etc/pkg.conf
#HANDLE_RC_SCRIPTS  : NO

I changed HANDLE_RC_SCRIPTS from NO to YES, and removed the comment from
the beginning of the line.

# grep HANDLE_RC_SCRIPTS /usr/local/etc/pkg.conf
HANDLE_RC_SCRIPTS  : YES

# portmaster spamassassin-3.4.0_9

[ building of spamassassin-3.4.0_9 removed ]

===>>> Re-installation of spamassassin-3.4.0_9 complete

===>>> Exiting
# /usr/local/etc/rc.d/sa-spamd status
spamd is not running.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
# /usr/local/etc/rc.d/sa-spamd start
Starting spamd.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   71309 5  tcp4   127.0.0.1:783 *:*
root perl   71308 5  tcp4   127.0.0.1:783 *:*
root perl   71307 5  tcp4   127.0.0.1:783 *:*
# /usr/local/bin/sa-check_spamd
SPAMD OK: 0.101 second ping repsonse time
# ps -U root -o pid,args|grep spam
71307 /usr/local/bin/spamd -c -d -r /var/run/spamd/spamd.pid (perl)
71308 spamd child (perl)
71309 spamd child (perl)
#

So now the spamassassin is stopped correctly, but it is not started
automatically.

-- 
"In the beginning the Universe was created. This has made a lot of
people very angry and been widely regarded as a bad move."
-- Douglas Adams 1952 - 2001
___
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"

Re: Spamd

[Matthew D. Fuller]

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 update
> spamassassin, using portmaster, which is using pkgng.

pkg-plist in spamassassin includes

@unexec rm -rf /var/run/spamd 2>&1 >/dev/null || true

so removing the package will blow away the pid file.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
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"