| Website | https://www.bsd.nl |
| IETF | https://datatracker.ietf.org/person/jo[email protected] |
| Github | https://github.com/job |
The final quotes sting everyone that's done architecture:
"The series began with a single engineer’s shock on his first day back in the organization.
"It ends with the same observation, now seen at every layer: the foundational problems in the node stack were visible, the operational and security consequences were measurable, and the proposed paths forward were concrete.
"At no level did those signals generate a response."
https://isolveproblems.substack.com/p/how-microsoft-vaporized-a-trillion
RE: https://labyrinth.social/@nash/116178591588359360
you ever write code so inefficient you have to secure 80% of the world’s DRAM production
I solved it by adding the following to the .container file:
ExecStopPost=/bin/sh -c '/usr/bin/journalctl -u rrdp-sync.service --invocation 0 >> /data/logs/$$(date +%%Y%%m%%d).log'
Thanks @jaseg for the hint
ok systemd experts, how the heck do I get the output of a oneshot container with LogDriver=passthrough into both journald _and_ a regular log file that's rotated daily? Similar use case as described here https://github.com/systemd/systemd/issues/38684#issuecomment-3221956220
I need simple log files for long term archiving
In the old world I'd just do "./program | tee -a /logs/$(date +%Y%m%d.log)"
RIP FX
We collected some texts from the community in memory of FX. You can find them here https://phenoelit.de/fx.html
Jeffrey Haas
Colin
joernchen 