Update gns3.service.systemd

[blueneekone]

In reference to bug #1918, the gns3.service.systemd file references ExecPath /usr/bin/gns3server which needs to be changed to /usr/local/bin/gns3server for the daemon/service to run without failure.

Please see the change I made to the service above.

[eantowne]

This was discussed in the #1918. The installation location is dependent upon installation method (PPA vs PIP/Source) https://github.com/GNS3/gns3-server/issues/1918#issuecomment-887933906.

Here is another version of the gns3.service.systemd that is used by the VM build, it has the path you are looking for.

As discussed in #1918 , @grossmj it would be great if both versions of the service file were present along with the additional options we discussed in that issue.

[blueneekone]

Will that work for installing in Ubuntu by default too? I did an install via the setup script and had this issue.On Oct 3, 2022 05:39, eantowne @.***> wrote: This was discussed in the #1918. The installation location is dependent upon installation method (PPA vs PIP/Source) #1918 (comment). Here is another version of the gns3.service.systemd that is used by the VM build, it has the path you are looking for.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[eantowne]

Not sure. I have never used the setup script. I usually install via PPA on Ubuntu and derivatives.

On Mon, Oct 3, 2022 at 09:06 Evan Waechtler @.***> wrote:

Will that work for installing in Ubuntu by default too? I did an install via the setup script and had this issue.On Oct 3, 2022 05:39, eantowne @.***> wrote: This was discussed in the #1918. The installation location is dependent upon installation method (PPA vs PIP/Source) #1918 (comment). Here is another version of the gns3.service.systemd that is used by the VM build, it has the path you are looking for.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-server/pull/2123#issuecomment-1265411059, or unsubscribe https://github.com/notifications/unsubscribe-auth/APZX5I3ILVSO25CN2TYLFU3WBLK5PANCNFSM6AAAAAAQ3ICMKQ . You are receiving this because you commented.Message ID: @.***>

-- Ean L. Towne

@.***

[blueneekone]

I followed the instructions to run GNS3 as a daemon and the location isn't set correctly in the service so it failed everytime I ran sudo systemctl start gns3.On Oct 3, 2022 07:31, eantowne @.***> wrote:

Not sure. I have never used the setup script. I usually install via PPA on

Ubuntu and derivatives.

On Mon, Oct 3, 2022 at 09:06 Evan Waechtler @.***>

wrote:

Will that work for installing in Ubuntu by default too? I did an install

via the setup script and had this issue.On Oct 3, 2022 05:39, eantowne

@.***> wrote:

This was discussed in the #1918. The installation location is dependent

upon installation method (PPA vs PIP/Source) #1918 (comment).

Here is another version of the gns3.service.systemd that is used by the VM

build, it has the path you are looking for.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are

receiving this because you authored the thread.Message ID: @.***>

—

Reply to this email directly, view it on GitHub

https://github.com/GNS3/gns3-server/pull/2123#issuecomment-1265411059,

or unsubscribe

https://github.com/notifications/unsubscribe-auth/APZX5I3ILVSO25CN2TYLFU3WBLK5PANCNFSM6AAAAAAQ3ICMKQ

.

You are receiving this because you commented.Message ID:

@.***>

--

Ean L. Towne

@.***

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>