Your message dated Mon, 1 Oct 2007 12:42:56 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#434663: 'man nfs' typos: "interupt" x 2,"occured" x 2, and
"forground" x 2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mount
Version: 2.12r-19
Severity: minor
Tags: patch
Found some typos in '/usr/share/man/man5/nfs.5.gz', see attached '.diff'.
Hope this helps...
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages mount depends on:
ii libblkid1 1.40.2-1 block device id library
ii libc6 2.6-2 GNU C Library: Shared libraries
ii libuuid1 1.40.2-1 universally unique id library
mount recommends no packages.
-- debconf-show failed
--- nfs.5 2007-07-18 13:08:44.000000000 -0400
+++ /tmp/nfs.5 2007-07-25 13:31:11.000000000 -0400
@@ -88,7 +88,7 @@
The default value is 7 tenths of a second. After the first timeout,
the timeout is doubled after each successive timeout until a maximum
timeout of 60 seconds is reached or the enough retransmissions
-have occured to cause a major timeout. Then, if the filesystem
+have occurred to cause a major timeout. Then, if the filesystem
is hard mounted, each new timeout cascade restarts at twice the
initial value of the previous cascade, again doubling at each
retransmission. The maximum timeout is always 60 seconds.
@@ -135,7 +135,7 @@
.I retry=n
The number of minutes to retry an NFS mount operation
in the foreground or background before giving up.
-The default value for forground mounts is 2 minutes.
+The default value for foreground mounts is 2 minutes.
The default value for background mounts is 10000 minutes,
which is roughly one week.
.TP 1.5i
@@ -236,7 +236,7 @@
.TP 1.5i
.I intr
If an NFS file operation has a major timeout and it is hard mounted,
-then allow signals to interupt the file operation and cause it to
+then allow signals to interrupt the file operation and cause it to
return EINTR to the calling program. The default is to not
allow file operations to be interrupted.
.TP 1.5i
@@ -325,7 +325,7 @@
After the first timeout,
the timeout is doubled after each successive timeout until a maximum
timeout of 60 seconds is reached or the enough retransmissions
-have occured to cause a major timeout. Then, if the filesystem
+have occurred to cause a major timeout. Then, if the filesystem
is hard mounted, each new timeout cascade restarts at twice the
initial value of the previous cascade, again doubling at each
retransmission. The maximum timeout is always 60 seconds.
@@ -373,7 +373,7 @@
.I retry=n
The number of minutes to retry an NFS mount operation
in the foreground or background before giving up.
-The default value for forground mounts is 2 minutes.
+The default value for foreground mounts is 2 minutes.
The default value for background mounts is 10000 minutes,
which is roughly one week.
.TP 1.5i
@@ -431,7 +431,7 @@
.TP 1.5i
.I intr
If an NFS file operation has a major timeout and it is hard mounted,
-then allow signals to interupt the file operation and cause it to
+then allow signals to interrupt the file operation and cause it to
return EINTR to the calling program. The default is to not
allow file operations to be interrupted.
.TP 1.5i
--- End Message ---
--- Begin Message ---
Version: 2.13
util-linux no longer delivers nfs.
lamont
--- End Message ---
