On Fri 04 Feb 2011 at 15:13:18 +0100, Pol Hallen wrote:
> How is the best way to deny and allow by time and date of user/s
> poweroff/reboot system?
>
> This client runs from 08am to 8pm. I have to deny all users reboot or
> poweroff
> within time, but user/s can reboot or poweroff this system
On Fri, Feb 4, 2011 at 4:41 PM, Boyd Stephen Smith Jr.
wrote:
> In <201102041513.18513.debenv...@fuckaround.org>, Pol Hallen wrote:
>>
>>How is the best way to deny and allow by time and date of user/s
>>poweroff/reboot system?
>
> You could try something involving a cron job switching between two
In <201102041513.18513.debenv...@fuckaround.org>, Pol Hallen wrote:
>How is the best way to deny and allow by time and date of user/s
>poweroff/reboot system?
Well, the standard security model for Linux systems doesn't really take time
into account. Also, sudo, which can be configured slightly m
On Fri, 04 Feb 2011 15:30:01 +0100, Pol Hallen scribbled:
> hi folks :)
>
> How is the best way to deny and allow by time and date of user/s
> poweroff/reboot system?
>
> This client runs from 08am to 8pm. I have to deny all users reboot or
> poweroff within time, but user/s can reboot or powero
On Fri, 04 Feb 2011 15:13:18 +0100, Pol Hallen wrote:
> How is the best way to deny and allow by time and date of user/s
> poweroff/reboot system?
>
> This client runs from 08am to 8pm. I have to deny all users reboot or
> poweroff within time, but user/s can reboot or poweroff this system from
>
hi folks :)
How is the best way to deny and allow by time and date of user/s
poweroff/reboot system?
This client runs from 08am to 8pm. I have to deny all users reboot or poweroff
within time, but user/s can reboot or poweroff this system from 8.01pm to
7.59am.
Thanks!
Pol
--
To UNSUBSCR
6 matches
Mail list logo