| 1 |
Duncan <1i5t5.duncan@×××.net> posted pan.2009.01.18.07.01.07@×××.net, |
| 2 |
excerpted below, on Sun, 18 Jan 2009 07:01:08 +0000: |
| 3 |
|
| 4 |
> I'd check the documentation for your kernel watchdog driver. My guess |
| 5 |
> is that there's a kernel command-line option to disable it at boot, and |
| 6 |
> something (a sysfs file or the like) you can prod later, to tell it to |
| 7 |
> start, which you could then add to the watchdog daemon service script if |
| 8 |
> there's not already provision for it. |
| 9 |
|
| 10 |
A bit more detail on this... |
| 11 |
|
| 12 |
FWIW, if you temporarily compile the driver as a module, you can use |
| 13 |
modinfo to see the parameters it can take. From memory (not reverified), |
| 14 |
if it's then compiled kernel-built-in, you can provide the same |
| 15 |
parameters you would at load time, on the kernel command line as |
| 16 |
mod_name:param or mod_name:param:value. There should be documentation on |
| 17 |
the driver as well -- check the help for the kconfig option and see if it |
| 18 |
says where to look under the kernel Documentation dir |
| 19 |
(so /usr/src/linux/Documentation/whatever) for more. Or just browse the |
| 20 |
Documentation dir yourself and see what's there. A lot of it is |
| 21 |
documentation for coders, but there's a surprising lot of info to be |
| 22 |
learned by sysadmins and others as well, just looking around and opening |
| 23 |
files that look interesting. |
| 24 |
|
| 25 |
-- |
| 26 |
Duncan - List replies preferred. No HTML msgs. |
| 27 |
"Every nonfree program has a lord, a master -- |
| 28 |
and if you use the program, he is your master." Richard Stallman |
Archives