On Fri, 19.04.13 22:01, Peter Li (chinasau...@gmail.com) wrote:
> On 04/19/2013 04:16 AM, Colin Guthrie wrote:
>
> >>When I then run `systemctl start wsgw; systemctl status wsgw` I get:
> >>
> >> wsgw.service - WebSockets Gateway for pianod
> >> Loaded: loaded (/usr/lib/systemd/syst
В Fri, 19 Apr 2013 22:01:41 -0700
Peter Li пишет:
> On 04/19/2013 04:16 AM, Colin Guthrie wrote:
>
> >> When I then run `systemctl start wsgw; systemctl status wsgw` I get:
> >>
> >> wsgw.service - WebSockets Gateway for pianod
> >>Loaded: loaded (/usr/lib/systemd/system/wsgw.se
On 04/19/2013 04:16 AM, Colin Guthrie wrote:
When I then run `systemctl start wsgw; systemctl status wsgw` I get:
wsgw.service - WebSockets Gateway for pianod
Loaded: loaded (/usr/lib/systemd/system/wsgw.service; enabled)
Active: active (running) since Thu, 18 Apr 201
'Twas brillig, and Peter Li at 19/04/13 07:06 did gyre and gimble:
> Greetings, I hope this issue is familiar to someone here. I wrote a
> unit file for a service called "wsgw". It starts fine with `systemctl
> start wsgw`, and `systemctl enable wsgw` goes smoothly, but the service
> doesn't star
Hi,
there were some bugs introduced and fixed recently, with regards
to parsing env. files, that could be relevant. What version
of systemd are you running, and what do the logs say?
Zbyszek
On Thu, Apr 18, 2013 at 11:06:43PM -0700, Peter Li wrote:
> Greetings, I hope this issue is familiar to s
Greetings, I hope this issue is familiar to someone here. I wrote a
unit file for a service called "wsgw". It starts fine with `systemctl
start wsgw`, and `systemctl enable wsgw` goes smoothly, but the service
doesn't start on boot.
My only diagnostic so far has been running `systemctl statu