Timeline for How to kill all sessions for a Linux user except first one, and limit users to one login session
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2016 at 8:40 | comment | added | cas | yeah, that's what i assumed he meant. | |
| Jun 24, 2016 at 8:36 | comment | added | Kusalananda♦ | It could be that he means "logging into" the application, i.e. starting it and entering some credentials or something. Anyway, XY. | |
| Jun 24, 2016 at 8:34 | comment | added | cas | @Kusalananda - yes, he did say that, I didn't notice that until you pointed it out. However, given the confusion of the OP and his inability to clearly express what he means and what he wants, I'm going to assume that he's mistaken on that point. In any case, this answer is still useful for applications with either no license limitations (but a wish to limit resource usage) or less insane limits - merely logging in shouldn't trigger use of a license, actually running the app should. | |
| Jun 24, 2016 at 8:18 | comment | added | Kusalananda♦ | The OP says "Just logging in causes a license to be used in this application." But you're right, there might be something in the license manager that can be tweaked. | |
| Jun 24, 2016 at 5:00 | history | answered | cas | CC BY-SA 3.0 |