Re: "setlogin failed" when using svn+ssh
- Problem solved :o)
Thank you for pointing out was was actually the problem for me.
It was the PATH variable that was the problem when using the opt-
version of svnserver but adding the correct PATH to .profile
unfortunately did'nt help.
I did solve it by adding
command "/opt/bin/svnserve -t" in the authorized_keys file but then I
could no longer log in with ssh and get a prompt.
The working solution for me was simply to add a soft link in /usr/bin
The haxx svn-server seams to be down so I don't know what was the
suggested workaround there.
--- In firstname.lastname@example.org, Björn Langels <yahoogroups@...>
> I'm sorry I forgot to tell you my slugos version...
> I'm running SlugOSbe 4.8 and have installed the optware svnserve
> version version 1.5.2 (r32768).
> You are right about that the setlogin failed error message is there
> every time I log in via ssh so that is probably not the cause as
> say. I'll try to figure out how to make sure the svnserve isthis
> reachabel in the path when I use svh+ssh.
> --- In email@example.com, Adam Baker <slug@> wrote:
> > BjÃ¶rn Langels <yahoogroups@> writes:
> > >
> > > When I try to connect to my optware subversion server I get
> > > error message on the command line:Unslung
> > >
> > > > sh: svnserve: not found
> > > > svn: Connection closed unexpectedly
> > >
> > > In the logs (/var/log/messages) it says:
> > >
> > > Oct 3 09:13:08 (none) auth.info sshd: Accepted publickey
> > > lxxxx from 82.xxx.xxx.xxx port 10455 ssh2
> > > Oct 3 09:13:08 (none) auth.err sshd: error: setlogin
> > > Function not implemented
> > > Oct 3 09:13:08 (none) auth.err sshd: error: channel 0:
> > > chan_read_failed for istate 1
> > You don't say what you are running optware on, I'll assume
> 6.x based onlikely
> > the setlogin message although the svnserve not found is more
> on SlugOS orinclude /opt/bin
> > OpenWRT.
> > The setlogin message is nothing to worry about - you should see
> those whenever
> > you log in with ssh. The svnserve not found would be my prime
> candidate for
> > examination - ssh sets up the path on the slug to
> for anworkaround
> > interactive login but I'm not sure if that works for the non
> interactive login
> > used to launch svnserve. If that is the problem then the
> > http://svn.haxx.se/dev/archive-2007-02/0204.shtml
> > should help.
> > The chan_read_failed messages are also bad news but could be the
> result of
> > svnserve not launching.