GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The journal might endanger your log data if it becomes corrupt and you don't actually log the data somewhere. Though, it's arguable whether this is the journal's fault.
The article that Hazel linked to points out that the service that can be crashed is not enabled in Debian, and so presumably in Debian-based distros, while Red Hat has a fix.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by justmy2cents
Does systemd have a webserver if I may ask in this thread?
The question makes no sense.
Systemd is an innit system -- if you're intersted it's worth reading up on as it's almost certainly going to be the default of the major distributions (Slackware, possibly, aside) for the next few years at least.
"systemd" is, in fact, an enchanted toadstool, secretly produced by Russian Hackers working for the Wicked Witch of the West!
It can turn all of your precious data into a frog!
Seriously, there is of course a big risk.
At least, talented group of software developer talk about it as possible toxic linux software, i.e. a menace which is spreading like a disease throughout the Linux world.
The question makes no sense.
Systemd is an innit system -- if you're intersted it's worth reading up on as it's almost certainly going to be the default of the major distributions (Slackware, possibly, aside) for the next few years at least.
On Mon, 08.10.12 14:50, Petr Pisar (ppisar at redhat.com) wrote:
> Am I the only one who raised his eyebrow when today's systemd update to
> systemd-194-1.fc18 pulled in libmicrohttpd and qrencode-libs?
The live-syncing logging logic that is available in 184 as a preview is
based on JSON and HTTP (in order to build as much on existing standards
as possible, and get best integration with other systems). In order to
keep the footprint low we decided to use an existing embeddable minimal
HTTP engine for that, rather than writing our own. Correspondingly the
microhttpd library is only pulled in by the journal gateway daemon,
which is responsible for the HTTP iface to the journal. We thought about
splitting this off into an individual package (and it would be really
easy to still do that), but as the code of libmicrohttpd is minimal, and
it doesn't pull in any deps beyond what is already in the minimal
installation set we didn't bother so far. Note that the code is not
enabled unless people do "systemctl enable
systemd-journal-gatewayd.service".
The QR code stuff is for showing a scannable QR code for the FSS sealing
key. It's a gimmick. In order to minimize footprint we actually made
sure that the qrencode pacakge got split up in order not to pull in any
additional packages into the basic set. It too is a really minimal dep,
pulling nothing else in that wasn't in the minimal installation set
already. Here too, was the option to implement our own thing, our own QR
encoding code or just use the existing solution whose code is quite OK,
whose deps are minimal, and which is quite well tested already. With the
qrencode package split-up we were quite happy with having a dep on it.
As somebody who removes the likes of avahi-daemon from my system that is interesting -- do you have a link to the original post describing the issue rather than the discussion? I can't seem to see any facts in there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
