ah! then maybe the easiest way is indeed to create the sockets yourself.
We had meant to add that support at some point but the need was never
present. If your patch works for you for now, feel free to continue
using it; I'll look into this at some point this week.
On 5 December 2016 at 09:30, Bor
John,
I am new to go language (coming from Java world) I want to debug with
breakpoints from IDE (and I was able aftet adding socket creation code).
Maybe I should run it with systemd and then attach to it from IDE?
On 5 Dec 2016 09:23, "John Lenton" wrote:
On 5 December 2016 at 08:58, Boris R
Disabling systemd socket (snapd.socket) is just half a task. You do not
really want systemd to run your service (snapd.service) as you are running
it already in debug mode from IDE. Another thing, activation library
expects systemd env variables (LISTEN_PID, LISTEN_FDS) to be set, so there
should
On 5 December 2016 at 08:58, Boris Rybalkin wrote:
>
> Is it possible to run snapd for debugging without systemd socket activation?
depends on what you mean. At the end of HACKING.md in the root of the
project there are instructions for how to run snapd by hand, using
systemd-activate:
https://g
Le 05/12/2016 à 09:58, Boris Rybalkin a écrit :
> Hello,
>
> Is it possible to run snapd for debugging without systemd socket
> activation ?
>
> There is a check here:
> https://github.com/snapcore/snapd/blob/master/daemon/daemon.go#L198
>
> Which seems to expect socket from systemd.
>
> I was able
Hello,
Is it possible to run snapd for debugging without systemd socket activation
?
There is a check here:
https://github.com/snapcore/snapd/blob/master/daemon/daemon.go#L198
Which seems to expect socket from systemd.
I was able to run and debug without systemd by adding explicit socket
creati
