NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""

NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""

Run this as any user (no root necessary) on any distro with systemd.

Spoiler:
Slide to unlock Your system will hang, and you'll be forced to unclean reboot

Pic related. Systemd devs would rather have a daisy chain of bullshit with a single point of failure than an init system that's actually a SYSTEM, not a rickety platform.

slide to unclock

>What
A fucking bug

>Status
Bug fixed within 60 minutes

>Implications
Systemd is ACTIVELY maintained

>OP
Is a computer illiterate fucktard

share rem please

not him but here

You are a week late with your shitpost freetard.

Is the red one a meme?

Yes

Broadcast message from systemd-journald@PHILOSOPHUS (Mon 2016-10-03 03:15:45 EEST):

systemd[1]: Caught , dumped core as pid 10718.


Broadcast message from systemd-journald@PHILOSOPHUS (Mon 2016-10-03 03:15:45 EEST):

systemd[1]: Freezing execution.

Is Arch great or OP just a restarted systemd-hater?

Actually I'm the idiot here. What OP meant with hang is the inability of rebooting using systemctl. That is systemd gets crashed. Pretty neat actually. It is like dosing pid 1.

Oh no, a bug that affects approximately ONE person was discovered and patched.

rabble rabble muh ddos

At least it isn't a privilege escalation bug who the fuck cares you can do worse just spawning processes quickly.

Why?

because K&R > 1TBS

Even Torvalds does this.

>He needs brackets for a single if statement
lol noob this isn't some fizzbuzz

How else are you going to introduce "accidental" vulnerabilities while still keeping plausible deniability?

Is this noob for real?

kys tripfag

Jokes on you I don't have a sister to kiss

kill yourself
just kill yourself

I'm a ghost tho

>you'll be forced to unclean reboot
>what is sysrq

OP REKT AND BTFO
FINISHED AND BANKRUPT
OP ON SUICIDE WATCH

:* Muah!

>SYSTEM WILL HANG
AHAHAHAHAHAHAHA

Can you try calling systemctl?

Why is systemd so based, Cred Forums?

Picture related

You don't call systemctl, you call units with it

Just try running systemctl user. If it times out then your systemd crashed. You can confirm it on journalctl then. If not, you're fine and your systemd has been fixed.

...

...

Dates back to The C Programming Language. Just looks nicer

>Lose argument
>Maximum butthurt
>Make a pasta thread
Wow some people have no life at all

Reboot Even If System Utterly Broken
Linux kernel is more resilient than a cockroach.

>I personally don't care about other operating systems, basically
>If people care, it's their problem

BASED Lennart