Inspired by the first replay to a post on openwrt [1] I renamed the
init script to gogoclient and it now works.
It looks like the init script is killed in the process, because it has
the same name as the daemon.
The real fix would probably be to use a pid file?
regards,
Uli
1) https://dev.openwrt
On Fri, Jan 02, 2015 at 06:28:10PM +0800, Ying-Chun Liu (PaulLiu) wrote:
> I think something wrong with init system. Maybe systemd?
Yeah, if systemd is involved, its usually systemd.
Unfortunately, they'll blame the process rather than systemd.
The fact it worked on a standard init but not systemd
On Fri, Jan 02, 2015 at 09:36:32PM +0100, Uli Luckas wrote:
> Same here.
> Is anyone looking into the issue? Anything I can do?
I'm not looking into it. I haven't used gogoc for a while since my ISP
uses native IPv6. I probably should orphan the package.
Anyhow, working out why the system fails,
Same here.
Is anyone looking into the issue? Anything I can do?
regards,
Uli
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I think something wrong with init system. Maybe systemd?
The following works:
$ sudo /etc/init.d/gogoc stop
$ sleep 60
$ sudo start-stop-daemon --start --exec /usr/sbin/gogoc --
Then gogoc runs perfect.
You can use
$ sudo start-stop-daemon --stop --signal HUP --exec /usr/sbin/gogoc
to stop the d
Package: gogoc
Version: 1:1.2-5
Severity: normal
Dear Maintainer,
When gogoc is called from init.d script (ie. invoke-rc.d gogoc start),
it exits after establishing the tunnel.
Yet if I call gogoc from command line (ie. I just run 'gogoc'), gogoc
remains running after the tunnel is est
6 matches
Mail list logo
