Hacker Newsnew | past | comments | ask | show | jobs | submit | nolta's commentslogin


You might like "Coming of Age in the Milky Way".


This looks perfect, thank you!



Thank you. This one looks like it was written by a human, or an AI on a reasonable compute budget.


3250? The H100 NVL product spec [1] says it can do ~8 PFLOPs of FP8.

[1]: https://www.nvidia.com/en-us/data-center/h100/


There will be multiple press events around the world (Germany, Mexico, Chile, China, Taiwan, Japan, US):

https://eventhorizontelescope.org/blog/event-horizon-telesco...


Isn't this what they did on the Armageddon movie?


"[L]ook at those folds!" I'm looking at the folds, and they got worse.

And take the cover of the Lorsch Gospels: the misshapen fingers, the bulging eyes, the blank expressions -- this is crude, not stylized. You get the sense that art is devolving back to the "archaic smile".


It recommends:

  # Configure idle time logout
  ClientAliveInterval <value in seconds>
but i don't think this is correct. AFAICT, this is a keep-alive mechanism, not a timeout. I don't think openssh has an option to kill idle sessions.


Correct. For that you would populate the variable TMOUT to a positive number in seconds and make that variable read-only

  grep ^read /etc/profile.d/timeout.sh
  readonly TMOUT=7200
This variable can also be set in tmux and gnu screen. People usually figure out fairly quick how to bypass the timer but it is handy when people console into servers via the drac/ilo and forget to log out. Some shells don't do anything with TMOUT so a bastion must only have vetted shells.


You are correct. This is widely copy/pasted bad advice and does the exact opposite of what the comment says.

It is not an idle timeout logout at all. Instead, it causes sshd to periodically send probes to the client. This has a couple of effects, most notably keeping tcp sessions "active" and frequently exchanging packets (this can be useful to keep connections through statefull firewalls alive if you are genuinely idle), and to rapidly detect and disconnect a client that has actually gone away.

I think the origin of this incorrect description is the CIS documents. They have the exact same gross mistake in them.

I think the ClientAlive probes are useful and should be on, but it's definitely not an "idle logout" as claimed.



Yeah, i had the same reaction. For example, meson couldn't find pybind11 until i added `pybind11-config --cmakedir` to CMAKE_PREFIX_PATH.


Here's a nice video with a little more detail on the difference between intensional/extensional: https://www.youtube.com/watch?v=bNG53SA4n48


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: