Falk Hamann wrote:
> On Tue, 20 Jun 2006 17:52:35 +0200
> Daniel Hokka Zakrisson <daniel@hozac.com> wrote:
>
>
>>Falk Hamann wrote:
>>
>>>I try to mount a smb-share at guest-start.
>>>It failed with: ".: invalid option -- n".
>>>
>>>#cat fstab.remote
>>>//fsuser/grp /home/messdb/fsuser smbfs
>>>uid=101,gid=users,username=user,password=XXX 0 0
>>>
>>>#vserver --debug vtest start
>>>++ /usr/sbin/chbind --silent --nid 181 --ip
>>>192.168.1.181/23 /usr/lib/util-vserver/secure-mount -a --chroot
>>>--fstab /etc/vservers/vmessdb/fstab.remote --rootfs no .: invalid
>>>option -- n
>>
>>Seeing the rest of the trace might help, what actually prints the
>>invalid option?
>>
>
>
> If I start the following command, it produce the same output.
> #vnamespace -e 181 /usr/sbin/chbind --silent --nid 181 --ip 192.168.1.181/23 /usr/lib/util-vserver/secure-mount -a --chroot --fstab /etc/vservers/vmessdb/fstab.remote --rootfs no
>
> .: invalid option -- n
>
> Who produce this output ???
>
> #find . -exec grep -I -H "invalid option" {} \;
> ./util-vserver-0.30.210/src/secure-mount.c: WRITE_MSG(2, "secure-mount: invalid option for '--rootfs': '");
> ./util-vserver-0.30.210/config.guess: echo "$me: invalid option $1$help" >&2
> ./util-vserver-0.30.210/config.sub: echo "$me: invalid option $1$help"
>
> Comes this output from util-vserver ? I can't imagine. See output of find !
> Or from kernelpatch ? Or from another binary, perhaps smbmount ?
>
> Any help is welcome. Falk
>
I'd guess smbmount. An strace -fF -o mount.trace vnamespace... should
help you pinpoint which binary is printing it.
-- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412 _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserverReceived on Wed Jun 21 14:42:44 2006