|
From: | Carl Sutton |
Subject: | Re: [gpsd-users] -G option on gpsd |
Date: | Tue, 25 Oct 2016 22:45:03 +0100 |
Systemd is hardly the best way to do things.On Tue, Oct 25, 2016 at 2:17 PM, Carl Sutton <address@hidden> wrote:> when I intend for systemd to stay the fsck away from a certain daemon.Which is exactly what it will do when its "disabled"... One simple command, handily provided.A group aimed at "users" should really be giving the best way to do things, not some hack job that 1) can go wrong and 2) cant be reversed/undoneOn 25 October 2016 at 22:01, Chris Kuethe <address@hidden> wrote:I know about disable; I prefer rm(1) when I intend for systemd to stay the fsck away from a certain daemon.--On Tue, Oct 25, 2016 at 1:43 PM, Carl Sutton <address@hidden> wrote:I hope not, because there are proper ways to do things like this. Just takes 2 minutes on google.eg:systemctl disable foo.serviceJust find the command for your system.Carl Sutton
dogmatic69.comOn 25 October 2016 at 21:38, Gary E. Miller <address@hidden> wrote:Yo Chris!
On Tue, 25 Oct 2016 13:26:53 -0700
Chris Kuethe <address@hidden> wrote:
> "netstat -tunlp" will show you what, if anything, is bound to port
> 2947. if I had to guess, I'd say it's systemd and its stupid
> gpsd.socket. Here's what I did to my machine to put gpsd under manual
> control
I like it. Care to write that up as a systemd howto?
RGDS
GARY
------------------------------------------------------------ ---------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
address@hidden Tel:+1 541 382 8588
GDB has a 'break' feature; why doesn't it have 'fix' too?
--GDB has a 'break' feature; why doesn't it have 'fix' too?
[Prev in Thread] | Current Thread | [Next in Thread] |