Re: Spamd

2014-04-03 Thread 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: reason 23 why we've moved to linux

2014-03-22 Thread Esa Karkkainen
On Sun, Mar 23, 2014 at 03:49:34AM +0900, Randy Bush wrote:
> and i have two 9 systems where i try to use freebsd-update.  also a
> time-consuming rabbit hole leading nowhere pleasant.  e.g.
> 
> # freebsd-update upgrade -r 9.2-RELEASE-p3

Lose the "-p3", because freebsd-update will get you to the lastet
patch level. If you don't like this behaviour, you can use svn.

So:

# freebsd-update upgrade -r 9.2-RELEASE

Please remeber, all hardware sucks, all software sucks.

If you think that some piece of HW, SW or FW does not suck, it is
because you have "acclimated" yourself to that piece of, oops I'm
starting to digress.

FWIW, I've been using FreeBSD since 1.x times and at that time I cursed
why ports would only work on 2.x, not on 1.x, because ports handed the
depenedcy hell when compiling that piece of, aand I'm digressing again.

-- 
"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: this time it's vim/distfiles

2009-07-29 Thread Esa Karkkainen
On Wed, Jul 29, 2009 at 02:59:56PM +0100, N.J. Mann wrote:
> Try changing distinfo accordingly.

You can use your favourite editor or run the following commands as root

# cd /usr/ports/editors/vim
# sed -I .orig -e 's/7\.2\.041%/7.2.041^/' distinfo

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