It is clear that different scenarios require different rules.
I have installed Fedora for three different friends. All at different physical
locations from my place. These people have no computer knowledge, so giving
them elevated permissions spells disaster. However they must to be able to
On Fri, Jul 27, 2012 at 11:09:03 +0200,
Karel Volný wrote:
if the user is local then DO NOT ask for admin privileges (else
the user will just cut the power supply which is worse than
killing others' running processes)
I'd prefer to keep that option. A local user would be less likely to powe
On Fri, Jul 27, 2012 at 6:09 AM, Karel Volný wrote:
> but the warning should not prevent _any_ eligible user from
> powering off/rebooting, it should just provide a possibility to
> reconsider
+1
FC
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.or
Dne Čt 26. července 2012 21:36:20, Adam Pribyl napsal(a):
> On Thu, 26 Jul 2012, ergodic wrote:
> > Karel your philosophy is correct. I have seen this issue
> > when my grandchildren complained that they could not turn of
> > their box after it was was upgraded to F-17. That is why I
> > filed Bu
On Thu, 26 Jul 2012, ergodic wrote:
Karel your philosophy is correct. I have seen this issue when my grandchildren
complained that they could not turn of their box after it was was upgraded to
F-17. That is why I filed Bug 843299.
Manny
While I understand the reasoning made by Karel, I ha
Karel your philosophy is correct. I have seen this issue when my grandchildren
complained that they could not turn of their box after it was was upgraded to
F-17. That is why I filed Bug 843299.
Manny
- Original Message -
Dne St 25. července 2012 11:46:51, Adam Williamson napsal(a):
Dne St 25. července 2012 11:46:51, Adam Williamson napsal(a):
> I just tested on two F17 machines and running 'reboot' as a
> regular user happily reboots the system even if root is logged
> in at VT2, no warning or authentication required. That does
> seem to make the 'protection' on the graphical
On Wed, 2012-07-25 at 14:12 -0400, ergodic wrote:
> Thanks for your reply Adam.
> Why then reboot does not complain? Reboot executes immediatly.
> All those directives link to consolehelper or to systemctl, which should ask
> for authentication if another user is logged.
I don't think that's co
On Wed, 25 Jul 2012, ergodic wrote:
Thanks for your reply Adam.
Why then reboot does not complain? Reboot executes immediatly.
All those directives link to consolehelper or to systemctl, which should ask
for authentication if another user is logged.
Well then the reboot is broken?
- O
Thanks for your reply Adam.
Why then reboot does not complain? Reboot executes immediatly.
All those directives link to consolehelper or to systemctl, which should ask
for authentication if another user is logged.
- Original Message -
On Mon, 23 Jul 2012, ergodic wrote:
> Executing pow
On Mon, 23 Jul 2012, ergodic wrote:
Executing poweroff in F-17 (x86_64 up to date) defaults to the "Authentication is
required for powering off the system while other users are logged in" snippet.
Only one user (user1) actually logged in, however results from "who" and
"users" show otherwise:
Executing poweroff in F-17 (x86_64 up to date) defaults to the "Authentication
is required for powering off the system while other users are logged in"
snippet.
Only one user (user1) actually logged in, however results from "who" and
"users" show otherwise:
# who
user1 :0 2012-07-23 13:04 (
12 matches
Mail list logo
