From: Darryl Ross (bofh_at_afoyi.com)
Date: Fri 16 Jan 2004 - 02:55:14 GMT

• Previous message: Herbert Poetzl: "Re: [Vserver] socket.c: Invalid argument"
• In reply to: Trevor Nichols: "Re: [Vserver] socket.c: Invalid argument"
• Next in thread: Herbert Poetzl: "Re: [Vserver] socket.c: Invalid argument"

Thanks to Herbert via IRC, we have now solved this problem. I noticed
Herbert posted a followup to our IRC conversation, so I won't repeat it.

Cheers
Darryl

Trevor Nichols wrote:

>I also had this problem on VSM, which I posted previously about. I spoke
>with Herbet on IRC and went through our setup. The conclusion was that
>for the setup, the v_sshd scripts was limiting the IP address that any ssh
>sessions could bind to (by default).
>
>Using chbind as a prefix to the commands allowed me to get around the
>problem and then the problem went away. This is a bit hacky, so in the end
>I removed the v_sshd scripts and use the bind option in sshd to correct
>it.
>
>Now we have no problems, in an identical manner to Rod. The interesting
>thing is getting a sshd running without readily available console access.
>:-)
>
>

_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

• Previous message: Herbert Poetzl: "Re: [Vserver] socket.c: Invalid argument"
• In reply to: Trevor Nichols: "Re: [Vserver] socket.c: Invalid argument"
• Next in thread: Herbert Poetzl: "Re: [Vserver] socket.c: Invalid argument"