1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
.TH diskseekd 1 "27Jan21" fdutils-5.6
.SH Name
diskseek, diskseekd - disk seek daemon; simulates Messy Dos' drive cleaning effect
'\" t
.de TQ
.br
.ns
.TP \\$1
..
.tr \(is'
.tr \(if`
.tr \(pd"
.SH Note
This manpage has been automatically generated from fdutils's texinfo
documentation. However, this process is only approximative, and some
items, such as cross-references, footnotes and indices are lost in this
translation process. Indeed, these items have no appropriate
representation in the manpage format. Moreover, only the items specific
to each command have been translated, and the general information about
fdutils has been dropped in the manpage version. Thus I strongly advise
you to use the original texinfo doc.
.TP
* \ \
To generate a printable copy from the texinfo doc, run the following
commands:
.nf
.ft 3
.in +0.3i
./configure; make dvi; dvips fdutils.dvi
.fi
.in -0.3i
.ft R
\&\fR
.TP
* \ \
To generate a HTML copy, run:
.nf
.ft 3
.in +0.3i
./configure; make html
.fi
.in -0.3i
.ft R
\&\fRA pre-made HTML can be found at:
\&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
.TP
* \ \
To generate an info copy (browsable using emacs' info mode), run:
.nf
.ft 3
.in +0.3i
./configure; make info
.fi
.in -0.3i
.ft R
\&\fR
.PP
The texinfo doc looks most pretty when printed or as HTML. Indeed, in
the info version certain examples are difficult to read due to the
quoting conventions used in info.
.SH Description
.PP
Several people have noticed that Linux has a bad tendency of killing
floppy drives. These failures remained completely mysterious, until
somebody noticed that they were due to huge layers of dust accumulating
in the floppy drives. This cannot happen under Messy Dos, because this
excuse for an operating system is so unstable that it crashes roughly
every 20 minutes (actually less if you are running Windows). When
rebooting, the BIOS seeks the drive, and by doing this, it shakes the
dust out of the drive mechanism. \fR\&\f(CWdiskseekd\fR simulates this effect
by seeking the drive periodically. If it is called as \fR\&\f(CWdiskseek\fR,
the drive is sought only once.
.PP
.SH Options
.PP
The syntax for \fR\&\f(CWdiskseekd\fR is as follows:
.nf
.ft 3
.in +0.3i
\&\fR\&\f(CWdiskseekd [\fR\&\f(CW\-d \fIdrive\fR\&\f(CW] [\fR\&\f(CW\-i \fIinterval\fR\&\f(CW] [\fR\&\f(CW\-p \fIpidfile\fR\&\f(CW]
.fi
.in -0.3i
.ft R
\&\fR
.TP
\&\fR\&\f(CW\-d\ \fIdrive\fR\&\f(CW\fR\
Selects the drive to seek. By default, drive 0 (\fR\&\f(CW\(if/dev/fd0\(is\fR) is sought.
.TP
\&\fR\&\f(CW\-i\ \fIinterval\fR\&\f(CW\fR\
Selects the cleaning interval, in seconds. If the interval is 0, a
single seek is done. This is useful when calling diskseek from a
crontab. The default is 1000 seconds (about 16 minutes) for
\&\fR\&\f(CWdiskseekd\fR and 0 for \fR\&\f(CWdiskseek\fR.
.TP
\&\fR\&\f(CW\-p\ \fIpidfile\fR\&\f(CW\fR\
Stores the process id of the diskseekd daemon into \fIpidfile\fR instead
of the default \fR\&\f(CW\(if/var/run/diskseekd.pid\(is\fR.
.PP
.SH Bugs
.TP
1.\
Other aspects of Messy Dos' flakiness are not simulated.
.TP
2.\
This section lacks a few smileys.
.SH See Also
Fdutils' texinfo doc
|
