My script assumes (requires) you to do a pip installation of weewx, so I have not looked into the differences if you try to use a dpkg installation (which runs as weewx) while building and installing rtlsdr etc. as a 'different' user, in your case user 'ace'. I suppose you could look into whether you could simply copy the built binary to someplace in user weewx's $PATH (editing user/group appropriately), but I'm wildly speculating basically. Be sure to edit weewx.conf if you move the built binary someplace other than where you have it now.
Just in case, lets see a "ls -lgd" of /home/ace to make sure you don't have permissions set to 700 or something like that which would I think be too tight for a different user (weewx) to be able to drill down to the stuff in /home/ace/go and below there. On Saturday, February 22, 2025 at 4:10:50 PM UTC-8 Wayne wrote: > Well, I did a recursive chown to change the group for all directories and > files in the ./go directory tree to weewx. Unfortunately upon starting > weewx it reports the identical driver permission error. > > I thought it could possibly be related to a runtime library (i.e. > librtlsdr). This library was built as part of the install script I followed > in the same /home/ace directory tree. But after the "make install" I did > "sudo ldconfig" which I understood to make any new libraries available to > everyone. If this is not the case, could that cause the file Permission > error? How can I test this theory? > > On Sat, Feb 22, 2025, at 4:17 PM, vince wrote: > > My wild guess is that the weewx user does not have permission to get > > down into /home/ace/go/bin to find the rtldavis executable. > > > > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/d40f8aac-1d8f-462a-b2d3-259194e2fdcfn%40googlegroups.com.
