• 3 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle

  • It has definitely changed, I don’t know when, but it’s been like this for at least the last decade.

    Though, in my experience (NB: I’m a software engineer, which is a notoriously lax field.) only what the piece of paper says has changed. Hell, most of my employee handbooks have claimed that “full time” is 50 hours a week. They get away with it because I’m classified as a “computer employee” (lol) and make more than $35k/year (super lol) which means my employment is exempted from minimum wage and overtime pay laws.

    Nobody that I know actually works that consistently. Most people I know don’t even do 40. I do 9-5 (or 8:30-4:30 usually), I take breaks when I need them and nobody has ever complained to me about the amount I’m working.

    My only guess for why it’s this way is that having that be the official working time means it’s easier to fire anyone for no reason because they’re not working their “contractually obligated” amount of time.






  • Hey, this might be something I’m interested in, but I’m not sure because there aren’t many details in your readme.

    Some questions I’d suggest you answer in the readme:

    [Edit: after looking through the code quickly, some of my questions probably don’t male sense because this seems to be an alerting style monitoring tool, not a observability style monitoring tool. Answering my own questions for others that are curious:]

    What does it monitor?

    [Disk space and CPU use]

    What is the interface? Web? It does compare itself to grafana, so maybe. TUI? Maybe that’s what makes it more light weight?

    [It doesn’t have one, it sends telegram messages when alarm thresholds(?) are hit.]

    Does it only work on Debian? If not, are there deps that are required that are installed as dependencies of the deb?

    [Looks like it should work anywhere, the ‘watchers’ use the nix crate and read procfs, so I assume that means it should work anywhere without depending on anything besides the Linux kernel.]

    Is there history or is it real time only?

    [Realtime only, well I guess there’s the telegram history.]

    What does it look like? (Honestly, a screenshot could possibly answer most of these questions and a whole lot more.)

    [It doesn’t look like anything. There’s no screenshot because there’s nothing to screenshot.]









  • IMO, yes. Docker (or at least OCI containers) aren’t going anywhere. Though one big warning to start with, as a sysadmin, you’re going to be absolutely aghast at the security practices that most docker tutorials suggest. Just know that it’s really not that hard to do things right (for the most part[1]).

    I personally suggest using rootless podman with docker-compose via the podman-system-service.

    Podman re-implements the docker cli using the system namespacing (etc.) features directly instead of through a daemon that runs as root. (You can run the docker daemon rootless, but it clearly wasn’t designed for it and it just creates way more headaches.) The Podman System Service re-implements the docker daemon’s UDS API which allows real Docker Compose to run without the docker-daemon.


    1. If anyone can tell me how to set SELinux labels such that both a container and a samba server can have access, I could fix my last remaining major headache. ↩︎