This is fixed in Focal and newer by
https://github.com/systemd/systemd/commit/114110cdf1a0ddba8238e0e10c520039281c5d6e.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
this is still an issue
** Changed in: systemd (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817627
Title:
systemd-analyze
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817627
Title:
Also in need of a fix. Trying to run a very simple and popular program
as a service and it's not working due to this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817627
I am also very interested in this fix; it is currently preventing
integration with a CI/CD pipeline for deploying my company's web app to
AWS cloud-based Ubuntu 18.04 servers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This affects each system where /tmp is *not* on tmpfs which affects a
lot of cloud-built servers and effectively prevents usage of systemd-
analyze verify in Ansible, Puppet etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
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
I can confirm that this bug is on Ubuntu 18.04.2 LTS with all package
installed. It happens on every machine I used 18.04 on.
So you can't use `systemd-analyze verify` to verify unit files on 18.04.
I think this need to be solved.
--
You received this bug notification because you are a member
I use separate mountpoint for /tmp directory and also am affected by
this issue on latest Ubuntu 18.04.2 with all package updates installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The commit fixing the issue is
https://github.com/systemd/systemd/commit/114110cd
Could you describe why you think it's an issue important enough to
justify a stable update, it seems only a warning but not having
consequences? Do you use a real mount for the /tmp directory?
--
You received this
Marking the Ubuntu Manpage Repository task invalid and adding the
systemd (Ubuntu) task.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-manpage-repository
Status: New => Invalid
--
You received this bug notification because you are a
12 matches
Mail list logo
