With a freshly-booted up to date trusty VM (ubuntu-trusty-daily-
amd64-server-20170130-disk1.img, then dist-upgraded for libssl1.0.0
openssl), simply installing systemd seems to be sufficient to cause the
file to exist.
ubuntu@pjdc-test:~$ ls -l /var/run/nologin
ls: cannot access
I forgot to mention that pam_nologin prints "System is booting up." and
fails non-root logins when /var/run/nologin exists, which is why that is
relevant. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Also no longer able to reproduce when installing systemd from tvoss's
PPA on a fresh VM (ubuntu-trusty-daily-amd64-server-20170131-disk1.img).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Since upgrading from artful to bionic, I noticed that /var/log/kern.log,
etc., were not being updated on my machine.
In comparing to another machine running a fresh install of bionic, I
discovered that this seems to be the culprit:
[agnew(etc)] ls -l
Public bug reported:
Version: 1:4.2.8p4+dfsg-3ubuntu5.9
We've observed the following crash on an Ubuntu 16.04 s390x nova-compute
host, apparently related to the VMs network interfaces coming and going:
Nov 11 01:40:34 s0lp3 ntpd[2426]: Listen normally on 542170 qvo8dd4fc29-b8
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1836236
Title:
9.4ubuntu4.9: Broken package because of
Public bug reported:
As of 1.5 (per apt-secure(8)) apt checks and warns if a repository's
Label value changes.
This probably makes sense for Debian, where folks may be tracking stable
instead of buster, and will want to be warned when stable starts
pointing somewhere else.
However, Ubuntu
7 matches
Mail list logo
