=== cpaelzer__ is now known as cpaelzer
[06:10] <cpaelzer> jamespage: ok, thanks
[06:10] <cpaelzer> jamespage: we'll need some time for the new DPDK in Debian anyway - if things work out I'll get in touch with you for a snapshot build of 2.13 then
=== jancoow9 is now known as jancoow
[09:25] <jamespage> cpaelzer: ok ounds like a plan
=== lotuspsychje_ is now known as lotuspsychje
[10:53] <nightuser> Hi folks. The main channel suggested to ask here. What's the right way of enabling auto-updates on a server? Still use cron or systemd timers?
[11:00] <mwhudson> nightuser: man unattended-upgrades (which uses systemd timers, at least in newer releases)
[11:18] <weedmic> nightuser: is that really what you want to do?  we (where I work) check which updates are available, if they can affect running items, is it worth the risk, etc. and above all - how to revert if it breaks something.  I'm talking servers, not workstations.  Just a thought
[11:19] <nightuser> weedmic: I believe that updates from security repo are safe enough. It's just a tiny VPS which I keep for myself, so I'm not risking anything really.
[11:21] <weedmic> safe v crippling are not the same thing - it was just a thought to consider - u need not listen to me at all
[11:25] <nightuser> weedmic: I understand your point. If it was something serious, I'd think twice before applying them, but for personal usage it's okay for me.
=== tinwood_ is now known as tinwood
=== vlm- is now known as vlm
=== vlm_ is now known as vlm
=== vlm_ is now known as vlm
=== vlm_ is now known as vlm
=== EdFletcherT137 is now known as cxzxczxcxzc