Bug 5677 - tl-show-licenses reports wrong license count if run as user
Summary: tl-show-licenses reports wrong license count if run as user
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Server (show other bugs)
Version: 4.4.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.10.0
Assignee: Karl Mikaelsson
URL:
Keywords: prosaic, samuel_tester
: 4389 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-10-16 14:48 CEST by Henrik Andersson
Modified: 2019-01-25 15:41 CET (History)
3 users (show)

See Also:
Acceptance Criteria:
* tl-show-licenses should show a message if a user does not have permissions to read the license files

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Henrik Andersson cendio 2015-10-16 14:48:10 CEST 
To report the correct license count, the user who executes tl-show-licenses needs to have read access to licenses files. If a user does not have read access to license files, the failure is silent and the result is incorrect count of licenses for the system.
Comment 5 Karl Mikaelsson cendio 2018-09-24 10:59:47 CEST 
It should now be clear to the user when tl-show-licenses isn't able to show the correct amount of licenses because of permission errors.
Comment 6 Samuel Mannehed cendio 2018-09-25 12:18:33 CEST 
Running tl-show-licenses as a non-privileged user with ThinLinc 4.9.0:

> $ /opt/thinlinc/sbin/tl-show-licenses 
> License summary: 5 concurrent users. Hard limit of 6 concurrent users. 
> ThinLinc version: 4.9.0

Running tl-show-licenses as a non-privileged user with the nightly build:

> $ /opt/thinlinc/sbin/tl-show-licenses 
> 2018-09-25 12:13:07 ERROR vsmserver.license: Insufficient permissions to read license files from /opt/thinlinc/etc/licenses
> License summary: 5 concurrent users. Hard limit of 6 concurrent users. 
> ThinLinc version: 4.9.0post

Looks good.
Comment 7 Karl Mikaelsson cendio 2019-01-25 15:41:05 CET 
*** Bug 4389 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.