[11:41] <wingarmac> greetings, can someone help me with css on a php page of my ubuntu apache server for intranet purpose? 
[11:41] <wingarmac> https://termbin.com/wbin I would like the system info and status both on 30% top split in 2 right and left with the iframe on th 70% bottom and page to fit to screen. But I can't get it to work as intended.
[11:42] <ravage> wingarmac: try #css
[11:44] <wingarmac> Well, there is css style into the php as you can see. But I mess with these div statement and get a mess with the tables. I do not know how to find what's wrong.
[11:45] <wingarmac> I tried several changes, but it gets even worse
[11:46] <ravage> it has nothing to do with ubuntu really
[11:46] <wingarmac> ravage you mean the css channel ? The message is already posted there, if that was your suggestion.
[11:47] <wingarmac> I've even tried gptchat, but it resets the other styles not related with the request in its suggestions, what makes it complicated to me again, to add these in the suggestions it made.
[12:02] <rbasak> wingarmac: your question isn't really appropriate for this channel.
[12:04] <wingarmac> I understand.
[12:04] <wingarmac> Thanks anyway
[16:25] <beowuff> Hello! I'm trying to get autoinstalls to work and I've run into an issue with the serial console. I can get everything to boot with pxe just fine, but when the installer starts, it shows a "basic mode" due to the serial connection and doesn't start the autoinstall. Is there a way to make the installer skip the "basic mode"?
[20:53] <ahasenack_> can someone enlighten me about systemd's socket activation again? I read https://www.freedesktop.org/software/systemd/man/systemd.socket.html but didn't find the info I want
[20:53] <ahasenack_> the service that the socket unit starts, is there a timeout for it to become inactive again? Like right after a boot, when just the socket unit is active, but the service not yet?
[21:12] <alkisg> ahasenack_: not sure if it helps, but in 23.04, `ssh localhost` => activates sshd, `ss -tunlp | grep :22` => lists both sshd and systemd, `killall sshd` => kills sshd, `ss` again => lists only systemd, which can still accept new connections and re-spawn sshd. So it feels like there's no timeout, but the process may exit on its own, and the socket will continue listening.
[21:13] <ahasenack_> sounds like it, it stays listening forever (sshd), after the first connection
[21:14] <ahasenack_> I know ssh.socket will always be listening
[21:14] <alkisg> I mean, if the process itself (in this example, sshd) has an "exit on idle" timeout, then systemd will still spawn it on the next connection
[21:16] <alkisg> But I don't think that systemd.socket has an option to kill spawned services on timeouts. I'm not even sure it can detect the traffic anymore after it handles the descriptor...
[21:16] <alkisg> *hands over
[21:16] <ahasenack_> I'm still thinking in terms of old inetd/xinetd
[21:19] <ahasenack_> I'm reviewing a ssh dep8 test, and don't understand how this check is passing: https://pastebin.ubuntu.com/p/ZjDdkPKnbg/ line 29
[21:19] <ahasenack_> because the test runs over ssh :)
[21:19] <ahasenack_> so ssh.service must be active
[21:19] <ahasenack_> I'm missing something
[21:19] <ahasenack_> and I confirmed it passes locally under autopkgtest
[21:20] <ahasenack_> but not when I run that script manually after copying it to a remote host, logging in via ssh, and running it
[21:23] <alkisg> If you connect via ssh, you'll start the service, so line 30 of that script will fail because sshd isn't inactive anymore...
[21:23] <ahasenack_> right, but it doesn't when I run the test with autopkgtest proper, which does use ssh to connect
[21:24] <ahasenack_> so what is going on :)
[21:24] <alkisg> Hmm...
[21:24] <ahasenack_> I triggered a "real" run in the launchpad infrastructure, https://autopkgtest.ubuntu.com/running#pkg-openssh
[21:24] <ahasenack_> it should be close to that part now
[21:25] <ahasenack_> I thought initially maybe there was a timeout, and given it takes ~30min to reach that test, maybe ssh.service would be dead by then, but clearly I don't understand how socket activation works for real
[21:40] <ahasenack_> test finished
[21:40] <ahasenack_> and failed
[21:41] <ahasenack_> logs: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ahasenack-ssh-rexec-sru/lunar/amd64/o/openssh/20230427_213242_59dbf@/log.gz
[21:41] <ahasenack_> let's see...
[21:41] <ahasenack_> yay, failed as expected