On Fri, 7 Jul 2006, Steinar H. Gunderson wrote:


On Thu, Jul 06, 2006 at 02:04:01PM +0200, Peder Chr. Norgaard wrote:
When upgrading til version 1:1.0.8+1.0.9pre1-1, my NIS-driven
automounter stopped working.  The log files had hundreds of entries from
automounter: "Unsupported nfs mount option: grpid".  I had to roll back
to 1:1.0.8-8 to be able to file this report ... I have fixed the
automatically generated "depends on:" below to show the installation
when the fault was manifest.

By the way, I just checked man mount, and I can't find any indication on what
"grpid" should mean for NFS -- it sounds ext2/ext3-only. Are you sure this
isn't a stray option being sent into your NFS mounts?

No, I am not sure - the content of the auto.master map is outside my control. But I will certainly investigate - I can put in a question at our IT department.

You are right, from the manual 'grpid' looks ext only. Nevertheless, even on an NFS mounted file system, the same kind of semantics - the groupid of a newly created file - has to be decided somehow. It is conceivable that the manual is wrong.

But I guess we have a reprieve now, with the recent decision to withdraw the mount.nfs program?

best regards
--
Peder Chr. Nørgaard             Senior System Developer, M. Sc.
Ericsson Denmark A/S, Telebit Division
Skanderborgvej 232              tel: +45 30 91 84 31
DK-8260 Viby J, Denmark         fax: +45 89 38 51 01
        e-mail: [EMAIL PROTECTED]
(old e-mail 2000-2003: [EMAIL PROTECTED])
         (old e-mail 1992-2000: [EMAIL PROTECTED])
----------------------------------------------------------------
This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution
is prohibited. If you believe this message has been sent to you in
error, please notify the sender by replying to this transmission and
delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we
only send and receive e-mails on the basis that we are not liable for
any such corruption, interception, amendment, tampering or viruses or
any consequences thereof.

Reply via email to