=== Napsterbater_ is now known as Napsterbater
=== cpaelzer__ is now known as cpaelzer
=== cpaelzer__ is now known as cpaelzer
=== mIk3_09 is now known as mIk3_08
=== jelly-home is now known as jelly
weedmicre:  intel-microcode 3.20191115.1ubuntu0.18.04.2 - pls provide link so I can see exactly what is going to change12:41
weedmicor, better, is this firmware change - or just software inside the kernel?12:42
martiansoulI want to record only the time when there is a cache hit and not a cache miss using curl. that's the value contained in `x-cache`(hit or miss) in response header.12:47
OerHeksweedmic, easy to find, https://launchpad.net/ubuntu/+source/intel-microcode/3.20191115.1ubuntu0.18.04.2 diff, changes12:51
weedmicexactly what I needed - appreciated12:53
weedmicbrb - needs a reboot12:54
OerHekshttps://usn.ubuntu.com/4182-4/ A regression was discovered that caused some Skylake processors to hang after a warm reboot.13:07
=== cpaelzer__ is now known as cpaelzer
evitI'm trying to setup Amazon SES for sending TLS enabled email. Using the documentation here https://docs.aws.amazon.com/ses/latest/DeveloperGuide/postfix.html19:50
evitEvidently the Amazon documentation is wrong and it is giving me an error...  cannot load Certification Authority data, CAfile="/etc/ssl/certs/ca-bundle.crt": disabling TLS support19:51
sarnoldcompare against https://help.ubuntu.com/lts/serverguide/postfix.html which should do a better job describing debian/ubuntu tls configs19:54
evitsarnold, Do I need to generate a TLS certificate?20:08
sarnoldevit: I'm not sure, I haven't hosted email in the modern era20:08
evitsarnold, I'm sending only through Amazon SES20:09
evitsarnold, When I switch my smtp_tls_CAfile to /etc/ssl/certs/ca-certificate.crt in main.cf it works without issue.20:11
WILYLP86hi everyone20:15
evitsarnold, This looks like the correct path https://www.webmoves.net/blog/build/send-email-from-ubuntu-linux-via-amazon-ses-3139/20:19
evitnow I get no errors and mail is flowing w/ TLS20:19
sarnoldvery nice, thanks for the link20:19
=== RoyK^ is now known as RoyK
tewardsarnold: i see email hosting questions20:28
teward... and I run my own email ;)20:28
tewarda little bit late I know but...20:28
sarnoldhey teward :)20:28
evitteward, Hi20:28
evitteward, Amazon SES documentation seems to be wrong on Ubuntu to SES config20:29
evitteward,  This looks like the correct path https://www.webmoves.net/blog/build/send-email-from-ubuntu-linux-via-amazon-ses-3139/20:30
evitteward, Correct CA file is sudo postconf -e 'smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt'20:30
evitAmazon doesn't have enough $$$ to have correct docs. =P20:30
tewardwell... in 18.04 /etc/ssl/certs/ca-certificates.crt *is* a valid path...20:31
tewardand unless you're blind, the section stating "If you use Ubuntu or a related distribution, type the following command:" is using the ***correct command*** you just stated20:31
tewardpoint 7 bullet point #220:31
sarnoldteward: the thing is that th e docs were written for rh-derivatives that use CAfile="/etc/ssl/certs/ca-bundle.crt": instead20:31
tewardsarnold: correction:20:31
tewardthere's multiple bullet points20:31
tewardand you have to ***actually read*** to know which command(s) to run ;)20:31
tewardso this is a case of PEBKAC and not reading the document properly20:32
evitteward, don't be a passive aggressive d-wad20:32
evitI see it now20:33
tewardthat wasn't my intention20:33
tewardbut if you want to call names20:33
teward*goes to do something else more productive with his time*20:33
pgndI've got an Ubu18LTS server up.  /boot is small. kernel HWE 18 *is* installed/enabled.  Kernels in place are 4.15.0-72, 5.0.0-36 & 5.0.0-37 (running).20:33
pgndIf I apt remove 4.15.0-72 & friends, the action is: "linux-generic linux-headers-4.15.0-72 linux-headers-4.15.0-72-generic linux-headers-generic linux-image-4.15.0-72-generic linux-image-generic linux-modules-4.15.0-72-generic linux-modules-extra-4.15.0-72-generic linux-tools-4.15.0-7220:34
pgnd  linux-tools-4.15.0-72-generic linux-tools-generic"20:34
pgndis it 'safe' to remove the unversioned "linux-generic" & "linux-headers-generic"?20:34
pgndor 4.15x in general?20:34
WILYLP86I have an active directory in samba4 and I need to know if there is any way to store a user's password in SSHA, or another type of hash20:35
sarnoldpgnd: those are how you get updates20:35
pgndsarnold: hi.  the 'generic' ones?20:36
sarnoldpgnd: yeah20:36
sarnoldpgnd: those meta-packages are updated to include dependencies on the new kernels when updates are released20:36
pgndHm.  So, since I *do* want updates that come along with the 18HWE, I'm stuck with keeping the 4.15.0x packages around? even though I'll NEVER use them?20:37
sarnoldpgnd: if you're running the HWE kernel then you can remove the release kernels, sure20:38
pgndsarnold: sry, I'm being dense.  If I do remove the release kernels, it rm's the 'generic' pkgs, as above.  Then updates don't work, iiuc.  But I *do* want updates ... of the HWE kernels.20:39
pgndor are THEY handled by different packates?20:39
sarnoldpgnd: yeah, they are, eg https://launchpad.net/ubuntu/+source/linux-meta-hwe20:39
pgndhm.  don't have any *meta* pkgs installed atm ...20:40
pgndlooking at the link20:40
sarnoldlinux-generic-hwe-18.04 perhaps?20:43
pgndah, so 'meta' is not in the naming ... looking at "Built Packages"20:43
sarnoldyeah, source package names don't have to match binary package names. It can be bloody confusing, and the ratsnest of kernel packages is the worst of the lot, I think20:44
pgndsarnold: ok, I've got: linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-hwe-tools-4.8.0-52 linux-image-generic-hwe-18.0420:45
pgndinstalled.  is that^ sufficient to safely REMOVE the 'release' 4.x kernel* ?20:45
lordcirth_Apt/.deb packages were never designed to have multiple versions installed in parallel, so the kernels with the versions in the names are hacky20:45
sarnoldI literally only make sense of these things because I've got a local archive mirror and can do things like ls -ld main/l/linux*/*hwe*   kinds of things20:45
pgndyeah, Ubu-space kernel naming is ... challenging.  Not my usual cup o' tea! ;-)20:45
sarnoldpgnd: that linux-hwe-tools-4.8.0-52 is ~2 years old, probably it can be removed..20:47
pgndlordcirth_: I'm generally in suse-land; bit simpler there.  or at least I understand it better :-)20:47
pgndhehe, "probably"!  u in Marketing? Sales? ;-p20:48
* pgnd holds breath while uninstalling. bets self $1 that it'll automagically reinstall itself, just to piss me off20:49
pgndThe recent upgrade from 16LTS to 18LTS was 'very greedy' about /boot space.  very Microsoft-like.  had to crib using /boot temporarily on an external USB.  woulda hoped that 250MB for a boot partition was enuf for an upgrade ...20:52
sarnoldoof yeah that's way too tight20:52
pgndwell, perspective.  the install process is way too fat!20:53
sarnoldeven post-install, 256 is going to give you a bad time20:53
pgndno clear reason it NEEDS GBs in /boot.  nah, production's just fine.20:54
pgnd that's /boot, NOT /root20:54
pgndwhich reminds me ... anyone KnowForCertain(tm) whether 18LTS can/does boot from /boot on RAID-1?  16LTS sure didn't ...20:55
sarnold512 megs should be enough for four ~60M initramfses, kernels, symbol maps..20:55
pgndsure.  clear how it scales.  just not clear why the installer had that demand.  water under the bride, anyway, now20:56
sarnoldpoor bride hope the dress didn't get soaked :)20:58
pgndheh, oops.20:58
sarnoldpgnd: there's just something that'll keep around ~four kernels during updates and upgrades and these things aren't small any more..20:58
sarnoldback inthe day I had a linux rescue floppy that could mount ntfs and fix winnt permissions problems.. 1.44 mb.. crazy.20:59
pgndyeah, yeah.  I'm 'spoiled'.  In suse it's trivial to specify multiinstalls, what & how many kernels are installed, kept, purged etc.21:00
pgndI typically keep boot on LV on RAID 1 or 10.  Then scaling to demand is trivial.  Physical partitions are an annoying PITA.  Which is why I'm looking/hoping (currently, not finding) re: Ubu18 boot on RAID support scope, if any.21:01
pgndrm'd the release kernels, rebooted. now, boot's @ "ext4  256M  128M  111M  54% /boot"21:04
pgndand no smoke! cool.21:04
sarnoldpgnd: there's something that's missing with raid in boot but I've never taken the time to understand it -- https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/146615021:15
ubottuLaunchpad bug 1466150 in grub-installer (Ubuntu) "grub-install breaks when ESP is on raid" [High,Triaged]21:15
sarnoldpgnd: /etc/kernel/postinst.d/apt-auto-removal /etc/apt/apt.conf.d/01autoremove-kernels may be useful to you too21:17
pgndsaw that. that's on EFI.  works fine here on "Other OS"; jhas for ages.  That said, on Ubu18, I'd settle for legacy/old-school ...21:17
pgndthx 4 the autorm refs21:18
pgndmy search-fu is NOT strong.  can't seem to find docs, or anecdotal evidence, that it DOES work on non-EFI.21:34
hggdhlsmod | grep btr23:12
hggdhdarn! sorry23:12

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!