Results 1 to 3 of 3

Thread: `systemctl start SERVICE` does not start all of SERVICE@*

  1. #1
    Join Date
    Sep 2020
    Beans
    3

    `systemctl start SERVICE` does not start all of SERVICE@*

    When I run `systemctl start openvpn` the `openvpn@server_tap` starts.

    But I created another server config `/etc/openvpn/server_tun` and another service `/etc/systemd/system/multi-user.target.wants/openvpn@server_tun.service` (copied from `openvpn@server_tap.service`) and this service does not start with `systemctl start openvpn`. I start it manually with `systemctl start openvpn@server_tun`.

    But when I run `systemctl stop openvpn`, both of them stop!

    I am not very familiar with systemd.
    Did not `openvpn.service` start all of `openvpn@*.service` variants created from me?
    What is wrong?
    How can I do this?

  2. #2
    Join Date
    Nov 2007
    Location
    London, England
    Beans
    7,301
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: `systemctl start SERVICE` does not start all of SERVICE@*

    I have a feeling there is some other file that says which config files openvpn should start by default. Maybe /etc/default/openvpn?
    I could be wrong, it's over ten years since I configured OpenVPN, but it may be worth checking out.

  3. #3
    Join Date
    Sep 2020
    Beans
    3

    Re: `systemctl start SERVICE` does not start all of SERVICE@*

    Execute
    systemctl daemon-reload
    then
    systemctl restart openvpn

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •