Public bug reported:
On Ubuntu 16.04.4 LTS
using
Package: systemd
Architecture: amd64
Version: 229-4ubuntu21.10
Changes the group membership are not picked up by the systemd process
for a logged-in user or for a user with enable-linger set regardless of
login status. Evidently the
Part of the mystery is solved and part not.
SOLVED:
The problem was that journal entries were not being stored on disk and
journalctl was not showing entries from memory.
The default Ubuntu config has settings
Storage=auto
SplitMode=uid
Also, the directory /var/log/journal does not exist by
This is related to https://github.com/systemd/systemd/issues/661
** Bug watch added: github.com/systemd/systemd/issues #661
https://github.com/systemd/systemd/issues/661
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Using
Ubuntu 16.04.4 LTS
and
Package: systemd
Architecture: amd64
Version: 229-4ubuntu21.10
Multi-Arch: foreign
Priority: required
Section: admin
Origin: Ubuntu
The journalctl(1) command cannot be used in a systemd OnFailure service
to get error logs. To replicate the
Public bug reported:
In
Description:Ubuntu 16.04.4 LTS
Release:16.04
using
adduser package Version: 3.113+nmu3ubuntu4
systemd package Version: 229-4ubuntu21.10
deluser will not clean up data in /run/user/ directory. If a user is
created then under many circumstances, such as
Public bug reported:
On Ubuntu version
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
and systemd package Version: 229-4ubuntu21.10
When the --full argument is used with systemctl edit a confirm prompt of
...some.service" already exists. Overwrite with "..."?
Public bug reported:
Report is for
Description:Ubuntu 16.04.4 LTS
Release:16.04
Package data is
Package: systemd
Architecture: amd64
Version: 229-4ubuntu21.10
Multi-Arch: foreign
No log file is applicable
The problem is that systemctl enable does not perform according to
No applicable logs
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
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:
The man page for the adduser utility clearly states the exit code
behavior to be expected as:
EXIT VALUES
0 The user exists as specified. This can have 2 causes: The user
was created by adduser or the user was already present on the system before
adduser was
9 matches
Mail list logo