Linux

48092 readers

1383 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

324

Systemd wants to expand to include a sudo replacement (outpost.fosspost.org)

submitted 6 months ago by starman@programming.dev to c/linux@lemmy.ml

261 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] topperharlie@lemmy.world 19 points 6 months ago (2 children)

hard disagree. life with plain text logs and daemon init scripts was so easy and nice. But we can't have nice things...

[–] atzanteol@sh.itjust.works 33 points 6 months ago (2 children)

Those hacked together system-specific bash scripts were shit. Having a standard way of creating, starting, ensuring restarts,and logging services is so much better.

You can still get all the plain text logs you like.

[–] baru@lemmy.world 6 points 6 months ago

Those hacked together system-specific bash scripts were shit.

With a different feature set per script as well. The systemd service files have often been pushed upstream.

Pretty sure people liking those scripts never really tried dealing with them across distributions. Though this just rehashes things that were said when distributions decided if to switch to systemd. Still the same strange claim that those scripts are somehow easier. It wasn't, it is also way easier to package a systemd file from upstream than to maintain that stuff within a distribution.

[–] trevor@lemmy.blahaj.zone 4 points 6 months ago (2 children)

How do you get plain-text logs instead of the garbage binary format that journalctl forces on you?

[–] 2xsaiko@discuss.tchncs.de 14 points 6 months ago (2 children)

Set ForwardToSyslog=yes in journald.conf and install a syslog daemon. Also optionally Storage=volatile (I wouldn't set Storage=none unless you want systemd to no longer show you any logs anywhere including in systemctl status because I assume it will do that)

[–] trevor@lemmy.blahaj.zone 5 points 6 months ago

Thank you!

[–] AA5B@lemmy.world -1 points 6 months ago

Definitely reads like a Microsoft answer, seems so much easier than just reading text

[–] atzanteol@sh.itjust.works 5 points 6 months ago* (last edited 6 months ago) (1 children)

By configuring journald to forward messages to syslog as is the default.

"forces on you" 🙄

Edit: Systemd has been around for 14 years. Did you never think to google this?

[–] 2xsaiko@discuss.tchncs.de 1 points 6 months ago

It's not the default fwiw. From journald.conf(5):

By default, only forwarding to wall is enabled.

[–] TimeSquirrel@kbin.social 19 points 6 months ago

You know what's nice? Being able to sit down at any Linux distro and being able to set up and configure services without Googling how to use that particular distro's init system.