diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2012-05-29 04:38:33 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2012-05-29 04:38:33 -0400 |
| commit | 5731350bb419502697d600b8fff91c220e68916f (patch) | |
| tree | 498ae1fb818ffea5d9e15a87804f4507665567d7 /packaging | |
| parent | f6017248affb97ea348d7c7733ad105f356af42a (diff) | |
| download | gpsd-5731350bb419502697d600b8fff91c220e68916f.tar.gz | |
Documentation improvent: warn about a problem encountered onm the OLPC.
Diffstat (limited to 'packaging')
| -rw-r--r-- | packaging/readme.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/packaging/readme.txt b/packaging/readme.txt index 62d57500..1f2d96cc 100644 --- a/packaging/readme.txt +++ b/packaging/readme.txt @@ -14,3 +14,11 @@ socket from a userland device manager. Accordingly, you probably want to set up a gpsd privilege group and make sure the Bluetooth device manager is in it. +If you see problems with gpsd being unable to get write access to +the USB or RS232 devices on your machine, it may be because after +startup, when it drops privileges, it moves itself from root to the +wrong group. gpsd normally figures out which group it should move +to by looking at the ownership of a prototypical tty (look in gpsd.c +for this code) but the owning user and group can be compiled in with +build-system options. + |