Crontabs can live in different places on different systems, but generally when you run crontab -e you're editing the crontab of the current user, which is generally placed in /var/spool/cron/{username}. If you do sudo crontab -e that edits the crontab/file for root. There can be other files nested in /etc/cron.d, /etc/cron.hourly, /etc/cron.daily et cetera as well.

To find out where those old cronjobs are still defined, you can recursive grep the name of that unique log file you mentioned (if the log file is part of the command in the crontab). grep -r "{unique log file name}" /etc and /var/spool should find it. If the log file name isn't in the command, grep for some other unique string from that cronjob that would stand out amidst everything else in /etc.

To add timestamps to log output, you can pipe it through ts.

"Trek: Deep Space Nine"

Best mostly just meaning it's the one I love the most - Ben Sisko and Kira Nerys are two of my favorite characters in tv, and were a big influence on me as a kid. I started rewatching recently for the first time since it originally aired, and man, it's still so good.

Trying to be more like LadyButterfly is a good place to start

Right now it's knitting and electronics - working on a deep blue shawl with sparkling beads in the pattern of a star chart, and wiring and coding up a pair of motion-reactive light-up pole dancing heels for my wife, fun stuff ❤️

The top ship is the USS Constituion, llaunched in 1797.

A trusted CA with a private key that's literally just the number 4. This is the funniest security incident of all time.

I prefer a Sofirn Q8 Plus - it's half a kilogram so it takes a lot of duct tape to secure it to the bars, but the 16000 lumens are worth it. Car cuts you off? Double click to just vaporize them.

I still listen to the Riven soundtrack, 29 years later. It's so rich and atmospheric, and composed and performed by one of the game's co-designers Robyn Miller.

Everything about that game was beautiful. Still holds up today.

You don't, is the short answer. Especially when the thing from github is unmaintained and unsupported on the current version of qubes:

Please note I currently do not have time to maintain Liteqube, it is not updated to support Qubes 4.2.

If you're just using qubes for funsies though and safety/security doesn't really matter, the qubes docs provide a very hacky method for copying files to dom0 (prefaced with a long "you really shouldn't do this" warning): https://doc.qubes-os.org/en/latest/user/how-to-guides/how-to-copy-from-dom0.html#copying-to-dom0

Not a disk issue, but looks instead like an issue with power management on that thunderbolt root port at 0000:80:1b.4. See this thread for proxmox-specific writeup: https://forum.proxmox.com/threads/kernel-7-0-x-regression-acs-violation-on-pcie-port-80-1b-4-causes-vm-freeze-%E2%80%94-arrow-lake-thunderbolt-5-intel-arc-b50-passthrough.184312/

And here for more: https://github.com/minisforum-docs/MS-02-Ultra/issues/10

Looks like you can resolve it for now by either reverting to 6.17.x kernel or creating a udev rule for the device.

I'm gonna submit an RFC for doing domain control verification, cert request, and cert issuance as part of the tls handshake. Unique certs for every session valid for 4 minutes.

...he also searched on his laptop for "command line to change local administrator password," "command line to remotely change local administrator password," and "how to remotely shutdown a computer usign cmd."

shittysysadmin criminal mastermind.