/srv/irclogs.ubuntu.com/2021/12/14/#ubuntu-server.txt

keithzgHmm so how would I make user systemd units actually start automatically? I have some defined like https://paste.ubuntu.com/p/JNyShVS87D/ but after both a `systemctl --user enable my-path-watching-thing.path` on them and a `sudo loginctl enable-linger keithzg` in case that was the issue, I still have to manually start them after reboots. I bet I'm missing *something* obvious, but I dunno what!00:45
sarnoldkeithzg: is there anything in journalctl about the units?00:48
keithzgsarnold: Just lines logging it automatically shutting down, the "-- Reboot --" lines, and then it logs when I manually start; that seems to be it.01:23
sarnoldkeithzg: hmm... do you have both the path *and* the service enabled?01:24
keithzgsarnold: The .path is enabled, the .service is not enableable; it just runs a script so I was under the impression I'd not need to have an [Install] section since it wasn't constantly running, but being intermittently triggered by the .path unit?01:37
sarnoldkeithzg: oh. hmm.01:37
sarnoldkeithzg: sure enough, a .service that I run via a .timer is also not enabled and doesn't have an [Install] section.01:38
=== gschanuel218 is now known as gschanuel21
=== genii is now known as genii-core
masonkeithzg: User services aren't intended to be used that way, generally. Typically you just want to have root manage a unit and set User=02:15
masonThat said, newer systemd might be doing it, thinking about user-run podman and similar.02:16
keithzgmason: Yeah in no small part this is me trying to be overly cute, heh, like hey if the service is running as the user I should be able to configure and handle it purely with user privs! And as per https://www.freedesktop.org/software/systemd/man/loginctl.html#enable-linger%20USER%E2%80%A6 it *should* be possible, at least from my reading of the docs (I could certainly be wrong!)02:24
keithzgSimply having a "User=keithzg" and plonking them down in /etc would certainly be the saner and easier approach!02:24
masonkeithzg: So, I was thinking of podman, and found this: https://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html02:25
masonkeithzg: I'm not sure what version of systemd is required for this to work, but skim that and scroll down at some point to "Installation of generated systemd unit files"02:25
masonRHEL 8 does it. Presumably newer Ubuntu does it. Not sure the best way to find out what's enabled and when.02:26
keithzgmason: Yeah that definitely mentions the same thing I figured was my silver bullet, `loginctl enable-linger <username>`, then the page's last updated bits being April 2020 gives me hope that it's not *too* new of a systemd version I'd need (also I didn't get any errors spat out by loginctl...). The server in question *is* on 20.04 though, so being too old wouldn't be super surprising.02:28
keithzg(I'll definitely keep podman in mind if I find myself dealing with Docker containers again! I remember it being surprisingly iffy to get those running automatically, although some of that could easily just be my unfamiliarity with Docker haha)02:30
masonkeithzg: Are you setting up ~/.config/systemd/user/foo ?02:30
masonkeithzg: And I'm pretty sure it Just Doesn't Work before some point, which is probably the critical thing once you're lingering and .configging and wolpertinging and such.02:31
masonkeithzg: There are some technical people here who can probably provide better answers if you stick around, anyway.02:32
keithzgmason: Yup, indeed ~/.config/systemd/user/my-thing.path and the like. And yeah I'm not going anywhere, and will be very interested if anyone else has any ideas! I may eventually just resort to User= lines and putting it in /etc like a normal person though haha02:41
=== not_phunyguy is now known as phunyguy
=== jgee1 is now known as jgee
=== mgedmin_ is now known as mgedmin
=== Avago_Broadqual0 is now known as Avago_Broadqual
=== LarsErik1 is now known as LarsErikP
=== ajfriesen7 is now known as ajfriesen
=== kdas_ is now known as kushal
winshithi there! i am hoping somebody can help me to get grafana-server to start on port 80? i created a systemd unit override and added three lines to it:11:29
winshitCapabilityBoundingSet=CAP_NET_BIND_SERVICE , AmbientCapabilities=CAP_NET_BIND_SERVICE as well as PrivateUsers=false11:30
winshitduring start of the service i still get "bind:permission denied"11:31
winshitits a ubuntu 20.04.3 lts server11:33
winshitcan somebody help me with that?11:34
=== masACC is now known as maswan
winshitanybody awake yet?12:56
winshitduring start of the grafana-server service i still get "bind:permission denied"12:56
winshiteven though i created a systemd unit override with: CapabilityBoundingSet=CAP_NET_BIND_SERVICE , AmbientCapabilities=CAP_NET_BIND_SERVICE as well as PrivateUsers=false12:56
winshitmy understanding is that those capabilities should suffice for grafana-sever to start on port 8012:57
=== thegodsquirrel is now known as theSantasquirrel
POQDavidHey guys i am running latest Ubuntu server and been trying to mount a nfs drive for backup and it keeps hangs while transfering large files what mount options is better to use like defaults,sync,rsize=65536,wsize=65536 is it any good?14:05
=== genii-core is now known as genii
mybalzitchBOOTS22:01
mybalzitchoops22:01

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