Update November 13, 2006:
Fixed the rpm’s. I was putting the –daemonize in with the other options. That does not work, putting it in first works.
So now I read the /etc/sysconfig/postgrey with
test -s /etc/sysconfig/postgrey && . /etc/sysconfig/postgrey
And execute
$POSTGREY_BIN –daemonize $OPTIONS
And all is right in the world.
Here are the links for the rpm and source rpm that I use on my SuSE 10.1 server.
Original October 4th post starts here.
————
I run OpenSuSE 10.1 on my server. For a few weeks yast’s online update was acting up. It would list things for update and not seem to fully get that the update was already.
Saturday I checked and got a boat load of new updates. One reboot later and yast online update is working perfectly each time.
I like packaging the software I use. It’s one way to keep my technical skills fresh and make my server more manageable. I use Postgrey with my postfix installation and have had problems wrapping the software. The software and RPM build fine, and I can run it by hand but when I try to read the /etc/sysconfig/postgrey in the init script, junk gets added to the command line.
I hacked the postfix init script and created a new script for postgrey.
I run postgrey like so:
/usr/sbin/postgrey
–unix=/var/spool/postfix/postgrey/socket
–daemonize –user=postgrey –pidfile=/var/run/postgrey.pid
In /etc/sysconfig/postgrey I have
OPTIONS=”–unix=/var/spool/postfix/postgrey/socket –daemonize –user=postgrey –pidfile=/var/run/postgrey.pid”
So in my init script I should be able to just do
. /etc/sysconfig/postgrey
And set OPTIONS that way. Once that’s done I should be able to just run
POSTGREY_BIN=/usr/sbin/postgrey
$POSTGREY_BIN $OPTIONS
The options piece seems to be adding on junk. The OPTIONS variable is set correctly but when I execute the perl script junk gets added and the postgrey script exits.
I’ve replaced $OPTIONS with explicit command line arguments for now but it’ll bug me till I figure it out.
