[00:50] <devster31> how do I know which packages will require reboot before installing them? and how can I install them without rebooting?
[03:20] <stooj> Hi all. I'm putting together a mail server but must have messed up somewhere. Using postfix + spamassassin + spamass-milter, communicating through a socket. But my mail.log contains the following every time the pipe is used:
[03:21] <stooj> May  2 05:44:41 myhostname postfix/smtpd[15597]: warning: milter unix:/spamassassin/spamd.sock: unreasonable packet length: 1397768525 > 1073741823
[03:21] <stooj> May  2 05:44:41 myhostname postfix/smtpd[15597]: warning: milter unix:/spamassassin/spamd.sock: read error in initial handshake
[03:21] <stooj> Anyone seen this before and recognise the problem?
[07:42] <[twisti]> it seems like since yesterday, everything on our LTS 12.04 server that is password related has become wonky
[07:42] <[twisti]> was there any problematic update or something like that ?
[09:22] <lordievader> Good morning.
[09:28] <Matsy> Good morning
[09:29] <lordievader> Hey Matsy, how are you?
[09:30] <Matsy> Good! Really enjoying my landscape environment
[09:30] <Matsy> I'm doing a semi-large tryout for landscape
[15:14] <seconds> Do you guys talk about Ubuntu server with open stack or thats another channel
[19:02] <kickit2> Hey everone - is there a way to force the system to wait for a connection to be established prior to continuing startup?  I have a VPN that must be connected before IP-tables loads, and right now, it launches open-vpn, but then continues right on.  The connection takes longer than for the system to get to iptables, and generates an error every time.
[19:14] <PryMar56> kickit2, look at the startup sequence numbers in /etc/rcS.d & /etc/rc2.d
[19:17] <PryMar56> kickit2, that situation is exactly what systemd does best
[19:23] <kickit2> PryMar56 - I have already changed that and it starting in the correct order, but calls to start openvp themselves are completed quite quickly - but the connection does not become active for a few seconds at least (even after the command finishes).  the problem is that the startup sequence just marches on and wants to apply iptables rules before the connection is active
[19:27] <PryMar56> kickit2, use something like this at tail of your NIC stanza in */interfaces: post-up /sbin/iptables-restore < /etc/iptables/rules