| Summary: | patch for lock (1) adding capability to lock all ttys | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | acid <acid> | ||||
| Component: | bin | Assignee: | yokota <yokota> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | 3.4-STABLE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
acid
1999-12-24 11:10:01 UTC
On Fri, 24 Dec 1999 12:59:56 +0200, acid@stu.cn.ua wrote: > .Bl -tag -width Fl > + .It Fl a > + Lock all ttys. To use this feature, you must be root or > + .Nm lock > + must be installed setuid to root. What I'd _really_ like to see as the lock_all feature with slightly different (and more useful) semantics: -a Lock all terminals for which the user has appropriate permissions. For the superuser, this means all terminals. I see no reason to allow a single user to lock all the terminals (including psuedo-terminals, no?) but I _do_ see a reason to allow a single user to lock all the terminals which that user owns. Wotcha think? Ciao, Sheldon. Responsible Changed From-To: freebsd-bugs->yokota Perhaps the syscons maintainer has already thought about this? Any comments? :-) State Changed From-To: open->closed This feature was recented implemented as the -v option. |