[Bug 1904321] [NEW] does not work as it should " systemctl edit service"

[erzent]

Public bug reported:

1. `systemctl edit service(elasticsearch)`
That creates file `/etc/systemd/system/elasticsearch.service.d/override.conf`

And I've added following section there:

[Service]
LimitMEMLOCK=infinity
LimitNPROC=32768
LimitNOFILE=250000


3. I've executed `systemctl daemon-reload; systemctl stop elasticsearch; systemctl start elasticsearch`

However those parameters were not applied to a newly started service and
I got an error "memory locking requested for elasticsearch process but
memory is not locked".

To workaround I've created a file
`/etc/systemd/system/elasticsearch.service.d/elasticsearch.conf` with
the same content and that fixed the problem.


ubuntu 18.04, all updates are installed

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1904321

Title:
  does not work as it should " systemctl edit service"

Status in systemd package in Ubuntu:
  New

Bug description:
  1. `systemctl edit service(elasticsearch)`
  That creates file `/etc/systemd/system/elasticsearch.service.d/override.conf`

  And I've added following section there:

  [Service]
  LimitMEMLOCK=infinity
  LimitNPROC=32768
  LimitNOFILE=250000

  
  3. I've executed `systemctl daemon-reload; systemctl stop elasticsearch; systemctl start elasticsearch`

  However those parameters were not applied to a newly started service
  and I got an error "memory locking requested for elasticsearch process
  but memory is not locked".

  To workaround I've created a file
  `/etc/systemd/system/elasticsearch.service.d/elasticsearch.conf` with
  the same content and that fixed the problem.

  
  ubuntu 18.04, all updates are installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904321/+subscriptions