This is a scary bug. I was just trying to verify the syntax of a timer
file using systemd v237. I got an error message back suggesting
something like rm -rf / was attempted to be executed instead!
$ sudo systemd-analyze verify /etc/systemd/system/my.timer
Attempted to remove disk file
> @xnox
> "The journald daemon has limits set for logs, meaning they will be
> rotated and discarded and should not cause out of disk-space errors."
>
> What are they? AFAICT it only has limits on the number of files, but
> not how big they can overall become.
The limits are documented in `man
I ran into this flooding today on Ubuntu 17.10. This "fixed" it, at
least temporarily:
pactl unload-module module-rtp-send
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I started a policy discussion on ubuntu-devel about whether systemd
journal logging should be persistent by default:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-November/040031.html
I encourage to participate. Non-developers can still participant, but
posts will be moderated (that's how
@dino99. Because good defaults matter. Being safe by default is
important. Being secure by default is important.
The "Principle of least surprise" applies here:
"In general engineering design contexts, the principle can be taken to
mean that a component of a system should behave in a manner
@dino99 how was "what most users prefer" prefer determined? Was there a
poll?
Systemd already has configuration options to limit the growth the the
journal. As documented in `man journald.conf`, the defaults are already
set to prevent filling up a disk.
If there were a poll, I can certainly
Thanks for the response, Martin.
Where will the public policy discuss take place?
Perhaps one possibility for a interim solution is for rsyslog to log to
journald by default instead of to disk by default and otherwise
maximally direct services to log into journald instead of rsyslog.
Mark
Public bug reported:
After upgrading 14.04 -> 16.04, key services are now running on systemd
and using the systemd journal for logging. In 14.04, key system logs
like /var/log/messages and /var/log/syslog were persistent, but after
the upgrade to 16.04 there has a been a regression of sorts: Logs
Aberto
This is marked as "fixed", but what was the fix?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1422143
Title:
No wifi connection after suspend with systemd due to
This fix works for me:
1. As root, create a file named /etc/systemd/system/resume.service with
the following contents:
[Unit]
Description=Local system resume actions
After=suspend.target
[Service]
Type=oneshot
ExecStart=/bin/systemctl restart NetworkManager.service
[Install]
I have this problem on a Dell XPS 2013 (Haswell) running Ubuntu 16.04.
However, trying to workaround it like results in an error:
sudo wpa_cli resume
Failed to connect to non-global ctrl_ifname: (nil) error: No such file
or directory.
This bug is the same as, or similar to:
No wifi
I started experiencing this bug after upgrading a Dell XPS 13 2013 (Haswell) to
16.04 and systemd.
After a resume, I have to do one of two things to re-connect to wifi:
1. Manually re-enable wifi in NetworkManager menu
2. sudo systemctl restart NetworkManager
--
You received this bug
I'm getting flooded with these errors on Ubuntu 16.04. My pulseaudo
package version is: 1:8.0-0ubuntu3
The exact error that floods my log is:
"[null-sink] rtp.c: sendmsg() failed: Invalid argument".
Looks like I get it more than 50 times /per second/.
--
You received this bug notification
In Bug #1521771, I spent some time tracking down different behavior
between the mysql-5.5 "init" and "upstart" scripts. They differ on how
many seconds are waited between the SIGTERM and SIGKILL signals are
sent. Different values can mean the difference between a slower clean
shutdown and a
That should nave been nologin.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1319973
Title:
libuuid needs a default shell (seems to not specify any?)
Status in
This remains a potential security issue with Ubuntu 14.04.
It appears that the util-linux (2.25-5) should set the login shell as
nologin. It seems here we need an update which finds the shells
already set as /bin/sh and resets them to nlogin
--
You received this bug notification because you are
16 matches
Mail list logo
