On Wednesday, April 21, 2021 at 6:41:27 PM UTC-7 Cameron D wrote: > Downsides? in reality, probably none as the likelihood of name clashes > are slim.
The system dirs are ahead of weewx in $PATH anyway, so the risk is miniscule if any exists at all. > However, it would probably be against the general principals, because > those are for all users on a system, while typically only a single user > might have permission to access the system. > > Actually it's exactly what the profile.d thing is for. It's for making system-wide changes and not requiring each user to take action themselves. Requiring users to take action themselves basically never works. They're simply not going to do that as the general rule. My suggestion is to make it more newbie proof so we don't even have to ask them. For that user the correct place would be in their own profile files. > Lean toward agree, 'if' the users would actually do so. History proves the vast majority do not. This is the underlying issue. We can't make new users who are disinclined to care about learning anything to actually try to learn anything. Also agree with Graham suggesting running weewx as a non-privileged user, but that's a bigger lift to make happen that I didn't want to suggest. Getting into that would require the pieces of weewx that talk to the /dev device to have appropriate privs to do so, and there might be portability issues there. > If they rely on sudo, then I don't think it sources those extra > /etc/profile.d files. > It's already sourced in in the non-privileged shell you ran sudo from, so that's not an issue. Tested on multiple variants of linux. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/480caa01-0bc6-4582-b279-9ac757b076e2n%40googlegroups.com.
