• 0 Posts
  • 107 Comments
Joined 1 year ago
cake
Cake day: July 29th, 2023

help-circle
  • mlg@lemmy.worldtolinuxmemes@lemmy.worldTerminating a process
    link
    fedilink
    English
    arrow-up
    46
    arrow-down
    1
    ·
    6 days ago

    Actually no, it’s just that the programs on Linux usually accept SIGINT, SIGTERM, etc pretty gracefully. Some are even smart enough to handle it on a thread hang. SIGKILL is last resort.

    Lots of Windows applications like to ignore the close request because Windows doesn’t have signals and instead you can only pass a window name to request exit which is the same as clicking the close button.

    So any hung software won’t respond and you have to terminate it.


  • mlg@lemmy.worldtolinuxmemes@lemmy.world`systemd` is all you need
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    8 days ago

    Systemd ignored my calendar override for the builtin raid scanner, so every week my server would chug to a halt to scan the entire array.

    In true systemd fashion, the documentation could not explain this behavior, so I had to make a full copy override instead of a merge override because reasons.


  • mlg@lemmy.worldtolinuxmemes@lemmy.worldNewbies never listen...
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    1 month ago

    Our crappy vendor software will only function if IPv6 is disabled network wide. Even if one machine has it enabled, the whole thing breaks

    Lol our former crappy vendor solution required to be run directly from AD Administrator. Pure luck the entire business didn’t collapse before we replaced it.

    A thread I read a long time ago on r/sysadmin







  • In a different article, he said he had issues with the ext4 maintainer who was acting high and mighty about C despite being responsible for a number of huge CVEs from code that he wrote.

    That being said, I don’t really see the benefit of rewriting modules in Rust.

    Technically, it’s still not a 1:1 replacement because Rust will many times not generate the exact same machine code as C, which does result in a small loss of speed (and in some small cases, vice versa).

    It’s acceptable for anything new, but unless there’s a notoriously painful part of the kernel, there’s no pont in redoing existing parts and even core userspace binaries.

    C quite literally makes you manipulate memory like a caveman holding a machine gun, but that’s important because it’s exactly what the machine is doing, which is required when you need to maximize efficiency. In Rust, you’d have to abstract some of that to the compiler to handle your logic which doesn’t match what a machine is doing. There is no such thing as “borrowing” and “ownership” in machine code.