On 7 January 2011 12:09, Marek Salwerowicz wrote:
>>
>> kldload nfssvc && dmesg | tail -n 10 ?
>>
>
> vm-salwerom% sudo kldload nfssvc
> kldload: can't load nfssvc: File exists
>
> but:
>
> vm-salwerom% sudo kldload nfssvc.ko
> vm-salwerom% dmesg | tail -n 10
> em0 at 194.29.146.128 server 194.29.
Ivan Voras writes:
> On 7 January 2011 20:15, Rick Macklem wrote:
>> Well, no UIDs on the wire inside the NFSv4 RPCs. Unfortunately, if
>> you are using AUTH_SYS, there are still UIDs in the RPC header. But
>> if you use krb5 then, yes, no UIDs on the wire.
>
> I was thinking about the practical
On 7 January 2011 20:15, Rick Macklem wrote:
>> On 01/07/11 15:47, Rick Macklem wrote:
>>
>> > What it needs to know is the domain name that you are using
>> > for bind, etc since that is appended to user and group names
>> > that go on the wire. For example:
>> > - If the machine's name is nfs-cl
>
> I was thinking about the practical scenario where users share a server
> - currently, as there's AFAIK no facility for remapping UIDs in
> FreeBSD, UIDs and usernames have to match on all machines. Will this
> change with NFSv4?
Unless you use Kerberized mounts (sec=krb5 or sec=krb5i or sec=k
> On 01/07/11 15:47, Rick Macklem wrote:
>
> > What it needs to know is the domain name that you are using
> > for bind, etc since that is appended to user and group names
> > that go on the wire. For example:
> > - If the machine's name is nfs-client.cis.uoguelph.ca as shown
> >by the hostnam
On 01/07/11 15:47, Rick Macklem wrote:
What it needs to know is the domain name that you are using
for bind, etc since that is appended to user and group names
that go on the wire. For example:
- If the machine's name is nfs-client.cis.uoguelph.ca as shown
by the hostname command...
--> t
I'm not very good at this stuff so others might need to chime in,
but it looks to me like some of your kernel modules are from different
builds.
I always:
# make KERNEL= install
after doing a kernel build, which copies the kernel and all the modules
to /boot/. I always use a other than "kernel"
> >
> > kldload nfssvc && dmesg | tail -n 10 ?
> >
>
> vm-salwerom% sudo kldload nfssvc
> kldload: can't load nfssvc: File exists
>
> but:
>
> vm-salwerom% sudo kldload nfssvc.ko
> vm-salwerom% dmesg | tail -n 10
> em0 at 194.29.146.128 server 194.29.146.27 server name amp2
> subnet mask 255.255
> > Try loading all of the modules one-by-one.
>
> so, after loading nfssvc.ko:
>
> vm-salwerom% sudo ./nfsuserd start
> Starting nfsuserd.
> vm-salwerom% sudo ./nfscbd start
> Starting nfscbd.
> nfscbd: Can't get fully qualified host name
This won't break the nfscbd, which you don't need unless
kldload nfssvc && dmesg | tail -n 10 ?
vm-salwerom% sudo kldload nfssvc
kldload: can't load nfssvc: File exists
but:
vm-salwerom% sudo kldload nfssvc.ko
vm-salwerom% dmesg | tail -n 10
em0 at 194.29.146.128 server 194.29.146.27 server name amp2
subnet mask 255.255.255.0 router 194.29.146.1 r
> Try loading all of the modules one-by-one.
so, after loading nfssvc.ko:
vm-salwerom% sudo ./nfsuserd start
Starting nfsuserd.
vm-salwerom% sudo ./nfscbd start
Starting nfscbd.
nfscbd: Can't get fully qualified host name
vm-salwerom% kldstat
Id Refs AddressSize Name
1 29 0xfff
On Jan 7, 2011, at 1:09 AM, Marek Salwerowicz wrote:
>>
>> kldload nfssvc && dmesg | tail -n 10 ?
>>
>
> vm-salwerom% sudo kldload nfssvc
> kldload: can't load nfssvc: File exists
>
> but:
>
> vm-salwerom% sudo kldload nfssvc.ko
> vm-salwerom% dmesg | tail -n 10
> em0 at 194.29.146.128 server
Hi all,
I am trying to run NFSv4 client on 64bit FreeBSD 9.0-Current.
I have inserted into /etc/rc.conf following lines:
nfsuserd_enable="YES"
nfscbd_enable="YES"
and after restart, during boot there is a meesage:
Jan 6 23:50:56 vm-salwerom root: /etc/rc: WARNING: failed to start nfsuserd
Jan
13 matches
Mail list logo