From: Marc Schmitt <mschmitt@inf.ethz.ch>
To: mschmitt@inf.ethz.ch
Cc: nfs@lists.sourceforge.net
Subject: Re: Large export list leads to "Invalid argument" errors when executing 'exportfs -r'
Date: 07 Jul 2003 12:14:56 +0200 [thread overview]
Message-ID: <1057572896.14659.16.camel@ikarus> (raw)
In-Reply-To: <1057405449.3361.64.camel@localhost>
I just wanted to add, I get many nfsd Security messages on the console,
too:
nfsd Security: //c bad export.
nfsd Security: //c bad export.
nfsd Security: //c bad export.
nfsd Security: /// bad export.
nfsd Security: //n bad export.
nfsd Security: //s bad export.
nfsd Security: //s bad export.
nfsd Security: //n bad export.
nfsd Security: //w bad export.
nfsd Security: //w bad export.
nfsd Security: //l bad export.
nfsd Security: //n bad export.
The directory structure for the homes described in the original post
does not match reality, it's:
/export/home/<first letter of login>/<login>
I guess the error messages above refer to <first letter of login>. But
there are no exports on the /export/home/<first letter of login> at all
in /etc/exports...
Regards,
Marc
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-07-07 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 11:44 Large export list leads to "Invalid argument" errors when executing 'exportfs -r' Marc Schmitt
2003-07-07 10:14 ` Marc Schmitt [this message]
2003-08-28 8:56 ` Marc Schmitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1057572896.14659.16.camel@ikarus \
--to=mschmitt@inf.ethz.ch \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.