/srv/irclogs.ubuntu.com/2017/02/12/#ubuntu-server.txt

tomreynjancoow: on 16.04, systemctl is part of systemd. you should defintely have it available as root. if not, it suggests that your upgrade did not work out well.00:32
tomreynthere are counter measures against hdd failures. one of them is RAID with a mirroring confiuguration - that's pretty easy if you can afford another disk. the other is to do backups, and do them properly and reliably, which you need to do either way.00:34
jancoowI replaced my serve casing00:56
jancoowi've 7hhd's in greyhole configuration00:56
jancoowthe only not redunant disk, the os drive, broke during the move...00:57
jancoowthe sata connectors littarly broke from the pcb and now th drive isn't spinning anymore00:57
jancoowLast backup is from 2 months ago..00:57
JanCthere shouldn't really be anything important on the OS drive, right?01:17
sarnolddrab: the best documentation of the difference of hash and bitmap might be the source code01:18
sarnolddrab: chances are you probably want one of the hash versions01:18
ChmEarlis it possible to run the early preseed script and modify the /etc/mke2fs.conf?06:18
ChmEarlor is there another way to set ext4 options in preseed?06:19
lordievaderGood morning.08:36
rbuxmornin09:19
gordonjcphi13:21
gordonjcpis there a way to get normal network interface names back in 16.04?13:21
gordonjcpat them moment they're all stuff like enp39asdfasdfblahblahblah and they change on every boot13:22
lordievadergordonjcp: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/13:22
lordievaderThey shouldn't change every boot...13:23
gordonjcpokay, why are they called "predictable" when they're essentially random13:23
lordievaderThey are named based on where the bios says they are.13:23
gordonjcpo_O13:23
gordonjcpthe bios has no idea what a network interface is13:23
lordievaderIt does know where the device is.13:24
lordievaderIn short, read the link I gave you.13:24
gordonjcpI'm reading it13:24
gordonjcpit seems like a pretty pointless change, which only makes things more difficult for users13:25
lordievaderIn my opinion it makes more sense than the old way.13:26
gordonjcprandomly assigning names to interfaces, based on when systemd gets around to looking at them?13:26
lordievaderThe point is that it is not random.13:27
gordonjcpokay, but it's not stable13:27
lordievaderIt is.13:27
gordonjcpit changes on every boot13:27
lordievaderThose ethX names werent. "Oh hey a new interface in the same location, lets give it a new name.13:27
lordievader"13:27
lordievaderAnyhow, these are just opinions.13:28
gordonjcpis there a way to get rid of systemd in 16.04?13:28
gordonjcpor if there isn't, is there a way to force it to work *exactly* like sysvinit13:28
gordonjcpright now it doesn't seem to run init scripts in any predictable order13:29
gordonjcp"oh hey, I can't see one of the network interfaces.  Never mind, I'll just start up dnsmasq on it, then I'll bring up the xl2tpd tunnel, oh hell everything on fire now"13:29
gordonjcpI guess that's a no13:33
gordonjcpso Ubuntu Server isn't actually intended for use on servers, then?13:33
gordonjcpor is there something fundamental I'm not getting about this13:34
drabsarnold: yeah I got some answers in #netfilter, turns out it's mostly a choice based on types and features14:46
drablooking closer it indeed makes sense for example bitmap:ip expects a range to be specified upon creation, something I hadn't noticed at first14:46
patdk-lapI would imagine bitmap to be much faster, as no hasing needed14:48
patdk-lapmore geared for matching against local network14:49
drabpatdk-lap: that's a good point, I hadn't thoguht of it, thank you15:18
SupaYoshiHi15:51
SupaYoshiHow do I upgrade my 12.04-LTS server to 16.04 LOTS15:52
SupaYoshi*LTS15:52
compdocI just didnt that for a system. worked great, and I was doing it over ssh15:58
compdocoh, wait. I think it was 14.04. nm16:00
=== JanC is now known as Guest86017
=== JanC_ is now known as JanC
lucidguyis it possible to rsnapshop backup to a windows/ntfs share?  I would think not since it relies on hard links.. no?17:34
xpistosHey all. I am having a bit of trouble with vim. I have several lines in the script that are formated mm-dd-yyyy like 01-01-2017, 01-08-2017 etc. how can I delete them all in one shot? I have tried g/^0?-*/d but that does not seem to work.18:50
xpistosAnd now that I think about it I will have like 10, 11 and 12 so even using ^0?-* wouldn't work anyway.18:51
=== ashleyd is now known as ashd
jancoowHi there. How to change this service into the new systemctl ? http://pastebin.com/8cnuJzZG20:11
DoowHi! I'm trying to set up some backup scripts and I noticed that the backup user don't have write access to its home directory (/var/backups) What's the reasoning behind this? What's the preferred workaround (my specific problem right now is that gpg can't create the .gnupg directory)21:22
patdk-lapheh?21:23
patdk-lapbackup user?21:23
patdk-lapthere is no backup user unless you created one21:23
patdk-lapand /var/backups isn't exactly something you want to backup, as it's outdated infomation, why it's called backups21:24
Doowpatdk-lap: I don't want to backup the contents of /var/backups, I want somewhere for my backup user to write metadata :)21:25
Doowpatdk-lap: are you 100% sure there's not a backup user by default? cause I have no memory of creating one and a 'random' person in #ubuntu had the exact same settings as me in his /etc/passwd21:26
Doowbackup:x:34:34:backup:/var/backups:/usr/sbin/nologin21:26
patdk-laphmm, I do have a backups user on this system21:27
DoowI could of course create a "backups2" user with its own home directory that I control, but it feels a bit silly. I don't want to change the current user without knowing why it's setup the way it is.21:30
DoowIn case I break something21:30
jancoowbackupgs "sigh"21:35
DoowIt looks to be a heritage from debian, they appearantly have an open bug from 2001 about it...21:42

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