On Friday, April 23, 2021 at 4:02:07 AM UTC-7 mwall wrote:
> i'm pretty settled about (1) - like tom said, if a user does setup.py,
> that user must at least understand PATH.
>
> if someone does not understand PATH, just refer him/her to the PATH wiki
> page.
>
>
I'd add use of sudo to that as w
I agree with mwall. Very astute and succinct.
On Friday, April 23, 2021 at 6:20:29 AM UTC-5 mwall wrote:
> a few more things:
>
> - sorry the last posting was so blunt - i've been close to the (currently
> uncooperative) machine the past few days, so i'm more used to talking to a
> computer th
a few more things:
- sorry the last posting was so blunt - i've been close to the (currently
uncooperative) machine the past few days, so i'm more used to talking to a
computer than to people. i mean no disrespect, and i *really* appreciate
all of the ideas and testing that vince, cameron, gle
a few thoughts:
1) a setup.py install should not touch any part of the system other than
the directory in which you install weewx. if you want udev rules,
logrotate, rsyslog, init.d/systemd, PATH, or anything else you do it
yourself. the weewx setup.py is not a typical python installation - i
On Wednesday, April 21, 2021 at 10:20:37 PM UTC-7 Cameron D wrote:
> Would the simplest option be to make more effort to discourage setup.py
> installs with a few warnings?
>
>
Think no. It's already discouraged. The problem is that the users ignore
the docs saying 'you need some skills to ins
On 22/04/2021, 'Cameron D' via weewx-development
wrote:
>
>
> On Thursday, 22 April 2021 at 2:34:11 pm UTC+10 Graham Eddy wrote:
>
>> maybe i did add the PATH mod myself - setting up systems so often for so
>> long that no doubt i do some things without thought…
>>
>
> Likewise - $HOME/bin is a st
perhaps make user demonstrate sufficient knowledge by making a few changes
(e.g. setting up PATH) before setup.py successfully executes? force users who
cannot show enough knowledge (or initiative to learn) to package install for
support reasons
> On 22 Apr 2021, at 3:20 pm, 'Cameron D' via wee
On Thursday, 22 April 2021 at 2:34:11 pm UTC+10 Graham Eddy wrote:
> maybe i did add the PATH mod myself - setting up systems so often for so
> long that no doubt i do some things without thought…
>
Likewise - $HOME/bin is a standard setup on my systems - I do recall seeing
it by default on a
>
> 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 ac
maybe i did add the PATH mod myself - setting up systems so often for so long
that no doubt i do some things without thought…
/var/log is no problem. rsyslogs(8) looks after perms, your rsyslog config
tells it what they should be, weewx sends all msgs to rsyslog to write them. my
weewx logs are
On Wednesday, April 21, 2021 at 6:50:03 PM UTC-7 Graham Eddy wrote:
> (the default on RPi is that $HOME/bin is added to PATH if it exists, so
> /home/weewx/bin gets picked up automatically when log in as weewx)
>
>
Not true in any version of the pi os (Raspbian) from early 2016 to current
that I
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 agains
another argument in favour of a dedicated user for weewx software. all my weewx
software runs as user ‘weewx’; i log in as weewx when i have a work session on
it
(the default on RPi is that $HOME/bin is added to PATH if it exists, so
/home/weewx/bin gets picked up automatically when log in as we
Downsides? in reality, probably none as the likelihood of name clashes
are slim.
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.
For that user the correct
I do think a bit of this is self-inflicted on our behalf. If you have a
look at the various command strings in the docs, the wiki, readmes for
extensions on GitHub etc you will see a lot that include no path with no
mention that a path may be required. This is fine for package installs but
setu
On Tuesday, April 20, 2021 at 8:20:35 AM UTC-7 Tom Keffer wrote:
> I really don't like the idea of messing with profiles, especially system
> profiles. There is nothing standard about them.
>
> Understanding how paths work is fundamental to using command lines. We
> will just have to insist tha
I really don't like the idea of messing with profiles, especially system
profiles. There is nothing standard about them.
Understanding how paths work is fundamental to using command lines. We will
just have to insist that users learn this minimum, especially if they are
doing a setup.py install. I
We continue to see 'many' posts where new unix/linux users simply don't
understand $PATH and how to get the non-standard /home/weewx/bin location
into their $PATH.
A quick fix would be to add a file to /etc/profile.d with the following
contents. I called mine /etc/profile.d/weewx-path.sh, but
18 matches
Mail list logo
