client reports wrong location of error log
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Invalid
|
Low
|
Unassigned | ||
| landscape-client (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: landscape-client
Landscape reports the error log is in ~/.landscape/
System information as of Sun Nov 2 09:50:01 EST 2008
System load: 0.89 Swap usage: 0% Processes: 163
Memory usage: 52% Temperature: 49 C Users logged in: 1
=> There were exceptions while processing one or more plugins. See
~/
Graph this data and manage this system at https:/
Last login: Sun Nov 2 09:48:25 2008 from deskaheh
ski@ganiodayo:~$ ls -l ~/.landscape/
ls: cannot access /home/ski/
ski@ganiodayo:~$ sudo ls -l /var/log/
[sudo] password for ski:
-rw-r--r-- 1 landscape root 138129 2008-11-02 09:50 /var/log/
ski@ganiodayo:~$
| Andreas Hasenack (ahasenack) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| 🤖 Landscape Builder (landscape-builder) wrote | #2 |
| Changed in landscape-client: | |
| status: | Confirmed → Invalid |
Correct. When using update-motd to display the sysinfo output, the tool runs as root, and so the logs are in the central location in /var/log/landscape. When run everytime the user logs in, it runs with the user privileges, which means the logs are then located in ~/.landscape/