mirror of
https://github.com/weewx/weewx.git
synced 2026-04-20 17:46:58 -04:00
improved table format for pip locations. per-platform status instructions.
This commit is contained in:
@@ -6,15 +6,36 @@ help you diagnose problems.
|
||||
|
||||
## Status
|
||||
|
||||
If WeeWX is running in the background, you can use the system's `init` tools
|
||||
to check the status. For example, on systems that use `systemd`, check it
|
||||
like this:
|
||||
```{.shell .copy}
|
||||
systemctl status weewx
|
||||
If WeeWX was configured to run as a daemon, you can use the system's `init`
|
||||
tools to check the status.
|
||||
|
||||
=== "systemd"
|
||||
|
||||
```{ .shell .copy }
|
||||
# For Linux systems that use systemd, e.g., Debian, Redhat, SUSE
|
||||
sudo systemctl status weewx
|
||||
```
|
||||
|
||||
=== "sysV"
|
||||
|
||||
```{ .shell .copy }
|
||||
# For Linux systems that use SysV init, e.g., Slackware, Devuan, Puppy
|
||||
sudo /etc/init.d/weewx status
|
||||
```
|
||||
|
||||
=== "BSD"
|
||||
|
||||
```{ .shell .copy }
|
||||
# For BSD systems, e.g., FreeBSD, OpenBSD
|
||||
sudo service weewx status
|
||||
```
|
||||
|
||||
Another way to see whether WeeWX is running is the `ps` tool. For example,
|
||||
this will tell you whether `weewxd` is running, and if it is, you will see the
|
||||
additional information including process identifier (PID), memory used, and
|
||||
how long it has been running.
|
||||
```
|
||||
On systems that use `sysV` init scripts, check it like this:
|
||||
```{.shell .copy}
|
||||
/etc/init.d/weewx status
|
||||
ps aux | grep weewxd
|
||||
```
|
||||
|
||||
## Reports
|
||||
|
||||
@@ -45,7 +45,7 @@ other stations.
|
||||
## Running as a daemon
|
||||
|
||||
For unattended operations it is best to have WeeWX run as a daemon, so that
|
||||
it is started automatically when the computer is rebooted.
|
||||
it is started automatically when the computer starts up.
|
||||
|
||||
If you installed WeeWX from DEB or RPM package, the daemon configuration is
|
||||
done automatically; the installer finishes with WeeWX running in the
|
||||
|
||||
@@ -83,9 +83,9 @@ the executables will depend on how the installation was done.
|
||||
| Install method | Commands | Location of executables |
|
||||
|-----------------------------------------------------|------------------------------------------------------------------------------|-------------------------|
|
||||
| Virtual environment<br/>(recommended) | `python3 -m venv ~/ve`<br/>`source ~/ve/bin/activate`<br/>`pip3 install weewx` | `~/ve/bin/` |
|
||||
| pip, no sudo, with `--user` | `pip3 install weewx --user` | `~/.local/bin/` |
|
||||
| pip, no sudo, no `--user` | `pip3 install weewx` | `~/.local/bin/` |
|
||||
| pip with sudo<br/>(not recommended) | `sudo pip3 install weewx` | `/usr/local/bin/` (1) |
|
||||
| Virtual environment with `--user`<br/>(not allowed) | `python3 -m venv ~/ve`<br/>`source ~/ve/bin/activate`<br/>`pip3 install weewx --user` | N/A |
|
||||
| pip<br/>no sudo<br/>with `--user` | `pip3 install weewx --user` | `~/.local/bin/` |
|
||||
| pip<br/>no sudo<br/>no `--user` | `pip3 install weewx` | `~/.local/bin/` |
|
||||
| pip<br/>with sudo<br/>(not recommended) | `sudo pip3 install weewx` | `/usr/local/bin/` (1) |
|
||||
| Virtual environment<br/>with `--user`<br/>(not allowed) | `python3 -m venv ~/ve`<br/>`source ~/ve/bin/activate`<br/>`pip3 install weewx --user` | N/A |
|
||||
|
||||
(1) Checked on Ubuntu 22.02 and Rocky v9.1
|
||||
|
||||
Reference in New Issue
Block a user