Hi Clemens,
>
> Hi, Roland!
>
> Please don't top-post.
sorry!
> > > [was: it would be easy to disable the kernel watchdog]
> > thanks, but i know i could do this.
>
> Good. I was also curious and just checked again. The watchdog subsystem
> is by default _disabled_ in the kernel
Hi, Roland!
Please don't top-post.
[EMAIL PROTECTED] schrieb:
> > [was: it would be easy to disable the kernel watchdog]
> thanks, but i know i could do this.
Good. I was also curious and just checked again. The watchdog subsystem
is by default _disabled_ in the kernel configuration. If you
Hi, Roland!
Please don't top-post.
[EMAIL PROTECTED] schrieb:
[was: it would be easy to disable the kernel watchdog]
thanks, but i know i could do this.
Good. I was also curious and just checked again. The watchdog subsystem
is by default _disabled_ in the kernel configuration. If you use
Hi Clemens,
Hi, Roland!
Please don't top-post.
sorry!
[was: it would be easy to disable the kernel watchdog]
thanks, but i know i could do this.
Good. I was also curious and just checked again. The watchdog subsystem
is by default _disabled_ in the kernel configuration. If you
.07 21:43:15
> An: [EMAIL PROTECTED]
> CC: Simon Arlott <[EMAIL PROTECTED]>, Robert Hancock <[EMAIL PROTECTED]>,
> linux-kernel@vger.kernel.org
> Betreff: Re: System reboot triggered by just reading a device file!?
>
> [EMAIL PROTECTED] schrieb:
>
> &
[EMAIL PROTECTED] schrieb:
> [was: reading /dev/watchdog triggers reboot as intended]
> need to change my own philosophy now, because i learned that reading isn`t
harmless. ;)
If you want to protect you from your curiosity (or from reading anything),
you could just disable the watchdog in
"Robert Hancock" <[EMAIL PROTECTED]>, linux-kernel@vger.kernel.org
> Betreff: Re: System reboot triggered by just reading a device file!?
>
> On Wed, November 21, 2007 00:01, [EMAIL PROTECTED] wrote:
> >>There is.. it's called "root privileges".
> > yes
: System reboot triggered by just reading a device file!?
On Wed, November 21, 2007 00:01, [EMAIL PROTECTED] wrote:
There is.. it's called root privileges.
yes, true.
but - regardless of being a windows app or not - what if you want to take a
look on your system as a whole
[EMAIL PROTECTED] schrieb:
[was: reading /dev/watchdog triggers reboot as intended]
need to change my own philosophy now, because i learned that reading isn`t
harmless. ;)
If you want to protect you from your curiosity (or from reading anything),
you could just disable the watchdog in the
PROTECTED], Robert Hancock [EMAIL PROTECTED],
linux-kernel@vger.kernel.org
Betreff: Re: System reboot triggered by just reading a device file!?
[EMAIL PROTECTED] schrieb:
[was: reading /dev/watchdog triggers reboot as intended]
need to change my own philosophy now, because i
On Wed, November 21, 2007 00:01, [EMAIL PROTECTED] wrote:
>>There is.. it's called "root privileges".
> yes, true.
>
> but - regardless of being a windows app or not - what if you want to take a
> look on your system as a whole,
> especially when using some tool which graphically shows how and
On Wed, November 21, 2007 00:01, [EMAIL PROTECTED] wrote:
There is.. it's called root privileges.
yes, true.
but - regardless of being a windows app or not - what if you want to take a
look on your system as a whole,
especially when using some tool which graphically shows how and where your
ert Hancock" <[EMAIL PROTECTED]>
> Gesendet: 21.11.07 00:35:23
> An: [EMAIL PROTECTED]
> CC: linux-kernel@vger.kernel.org
> Betreff: Re: System reboot triggered by just reading a device file!?
>
> [EMAIL PROTECTED] wrote:
> > good evening,
> >
> &
On Wed, Nov 21, 2007 at 12:06:57AM +0100, [EMAIL PROTECTED] wrote:
> - be root
That's your first mistake.
> - cat /dev/watchdog or dd if=/dev/watchdog of=/dev/zero bs=1 count=1 or .
> - wait one minute
>
> *reboot*!
And that's the defined behavior of /dev/watchdog, yes. Many
[EMAIL PROTECTED] wrote:
good evening,
i stumbled over some funny issue when trying windirstat (like KDirStat) with
wine.
after running that tool for a while my system rebooted. i could reproduce this
with every run.
after some deep investigation (i thought i had stability issues with my
good evening,
i stumbled over some funny issue when trying windirstat (like KDirStat) with
wine.
after running that tool for a while my system rebooted. i could reproduce this
with every run.
after some deep investigation (i thought i had stability issues with my system
and spent more than
good evening,
i stumbled over some funny issue when trying windirstat (like KDirStat) with
wine.
after running that tool for a while my system rebooted. i could reproduce this
with every run.
after some deep investigation (i thought i had stability issues with my system
and spent more than
[EMAIL PROTECTED] wrote:
good evening,
i stumbled over some funny issue when trying windirstat (like KDirStat) with
wine.
after running that tool for a while my system rebooted. i could reproduce this
with every run.
after some deep investigation (i thought i had stability issues with my
On Wed, Nov 21, 2007 at 12:06:57AM +0100, [EMAIL PROTECTED] wrote:
- be root
That's your first mistake.
- cat /dev/watchdog or dd if=/dev/watchdog of=/dev/zero bs=1 count=1 or .
- wait one minute
*reboot*!
And that's the defined behavior of /dev/watchdog, yes. Many years too
An: [EMAIL PROTECTED]
CC: linux-kernel@vger.kernel.org
Betreff: Re: System reboot triggered by just reading a device file!?
[EMAIL PROTECTED] wrote:
good evening,
i stumbled over some funny issue when trying windirstat (like KDirStat)
with wine.
after running that tool
20 matches
Mail list logo
