Threads for noqqe

  1. 5

    I can recommend https://uptimerobot.com/ (free version).

    Its independent from your infrastructure and can notify via mail (or twitter DM if you run your on mailserver on the servers you want to monitor)

    1. 1

      Doesn’t seem to monitor CPU usage, disk space usage and network traffic

    1. 1

      This gag product seems to exist entirely as an excuse to sell t-shirts. I wish I’d thought of it.

      1. 1

        actually people asked for tshirts and we added it after 2 years to the website :P

        (author here)

        1. 1

          That’s cynical of me, then. Either way, please take my words as admiration!

          1. 1

            no worries :)

            The shop works like this: A friend of mine made the webshop for the shirts and stuff. I have no access to it. Everytime there were some purchases he gives me a call and invites me to dinner from the money. Happend 5-7 times in the last 7 years so and we always had fun :)

      1. 4

        I’m so curious what openbsd devs are going to do with this (great) patch

        1. 5

          Review it.

          1. 2

            Me too. It’ll probably be the most interesting patch review round for wireguard.

          1. 1

            The $HOME dir layout I prefer (not my blog): https://morr.cc/home-sweet-home/

            1. 2

              I’m writing a small typing trainer in Go to get used to my NIU 40% keyboard

              https://github.com/noqqe/typist

              1. 1

                https://noqqe.de - German(!) Topics: OpenBSD, Sysadmin, Python, Photography, Linux

                1. 2

                  Has anyone used this wm and can compare it to i3?

                  1. 2

                    It was my main driver back in the ye olden days. The key is that it’s manual. The layout is entirely up to your discretion. You split a pane, resize the halves, rinse, launch a window in whatever pane, and repeat. i3 from the looks of it is more automatic and limited in ways you can split. Plus herbstluftwm is configured using shell scripts.

                    1. 1

                      you technically can script i3 via i3-msg but it’s inadvisable in a lot of places

                      1. 1

                        So it’s kind of like ratpoison or stumpwm.

                      2. 1

                        yep, me. Very happy with it!

                      1. 10

                        Some developer who obviously never maintained a production system advices people to

                        • spend money on a Webservice for some other type of logging
                        • “Just don’t write bugs”
                        • Dont care about code which fails because is not necessary (why is this code in the code base then?)

                        Disclaimer: Im a sysadmin maintaining tons of applications in different languages from software projects which are black boxes to me. Im happy for every single line of log output and its my responsibility to make maximum use out of those log lines given to me by friendly developers.

                        1. 3

                          As a developer who does maintain a production system, there is an alternative to logging which has fully replaced it (in my usage, at least).

                          I use honeycomb, but anything built on the same basic concept would be comparable.

                          However, this only really works well when A) developers are investigating system outages in the systems they write, and B) that you can get a new diagnostic line into production in under 15 minutes.

                          1. 1

                            You basically put in words perfectly what I wanted to say but wasn’t able to express properly - also from my perspective as a developer, who not so rarely needs to debug some tricky production issue.

                          1. 1

                            This isn’t stein from jcs.org, is it?

                            1. 2

                              I don’t think so, because @jcs is a OpenBSD dev, while this person says “[a few weeks ago …] I didn’t know much about OpenBSD”, in the introduction.

                              1. 2

                                No he is not jcs :)