* RE: SSHD 3.4 : cannot start a different service from the shell
@ 2002-09-10 2:01 Vince Hoffman
2002-09-10 3:44 ` Jochen Wiedmann
0 siblings, 1 reply; 4+ messages in thread
From: Vince Hoffman @ 2002-09-10 2:01 UTC (permalink / raw)
To: 'Jochen Wiedmann', cygwin; +Cc: voss
Could this be another issue with pub key auth ? (wild speculation only)
-----Original Message-----
From: Jochen Wiedmann [mailto:joe@ispsoft.de]
Sent: 10 September 2002 07:52
To: cygwin@cygwin.com
Cc: voss@vocalweb.de
Subject: Re: SSHD 3.4 : cannot start a different service from the shell
Ulrich Voss wrote:
> I have a slightly different problem than everybody else after
> upgrading to the newest version of OpenSSH (3.4p1). SSHD starts
> fine and I can login as before. But I can't start another service after
> logging on the machine.
> I user SSH for tunneling VNC traffic. I have normally switched off
> vnc for various reasons and start it after logging in with "net start
> winvnc". This worked fine for months now, but after upgrading to
> OpenSSH 3.4 I get the error "System Fehler 5 aufgetreten" which
> should translate to sth. like "system error 5 has occured". I can
> start and stop winvnc from the local console fine. Only when logged
> in remote via ssh I get this error.
I can confirm the problem, no solution though. Sorry. However, I
can supply an additional piece of information.
The problem seems to be related to the NT security. On the box in
question I have two users in group administrators: One local user
and a remote user (my NT domain user). Both can stop and start
services when logged in via PCAnyWhere. The former can when logged
in via SSH, the latter cant.
Any hint welcome,
Jochen
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: SSHD 3.4 : cannot start a different service from the shell
2002-09-10 2:01 SSHD 3.4 : cannot start a different service from the shell Vince Hoffman
@ 2002-09-10 3:44 ` Jochen Wiedmann
0 siblings, 0 replies; 4+ messages in thread
From: Jochen Wiedmann @ 2002-09-10 3:44 UTC (permalink / raw)
To: Vince Hoffman; +Cc: cygwin
No,
as written in a separate mail (with the wrong subject, though,
sorry! :-) it was caused by the permissions of /var/empty.
After changing them from 700 to 755 it now works perfectly well.
Regards,
Jochen
Quoting Vince Hoffman <Vince.Hoffman@uk.circle.com>:
> Could this be another issue with pub key auth ? (wild speculation only)
>
> -----Original Message-----
> From: Jochen Wiedmann [mailto:joe@ispsoft.de]
> Sent: 10 September 2002 07:52
> To: cygwin@cygwin.com
> Cc: voss@vocalweb.de
> Subject: Re: SSHD 3.4 : cannot start a different service from the shell
>
>
>
> Ulrich Voss wrote:
>
> > I have a slightly different problem than everybody else after
> > upgrading to the newest version of OpenSSH (3.4p1). SSHD starts
> > fine and I can login as before. But I can't start another service
> after
> > logging on the machine.
>
> > I user SSH for tunneling VNC traffic. I have normally switched off
> > vnc for various reasons and start it after logging in with "net start
>
> > winvnc". This worked fine for months now, but after upgrading to
> > OpenSSH 3.4 I get the error "System Fehler 5 aufgetreten" which
> > should translate to sth. like "system error 5 has occured". I can
> > start and stop winvnc from the local console fine. Only when logged
> > in remote via ssh I get this error.
>
> I can confirm the problem, no solution though. Sorry. However, I
> can supply an additional piece of information.
>
> The problem seems to be related to the NT security. On the box in
> question I have two users in group administrators: One local user
> and a remote user (my NT domain user). Both can stop and start
> services when logged in via PCAnyWhere. The former can when logged
> in via SSH, the latter cant.
>
> Any hint welcome,
>
> Jochen
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: SSHD 3.4 : cannot start a different service from the shell
@ 2002-09-10 0:10 Jochen Wiedmann
0 siblings, 0 replies; 4+ messages in thread
From: Jochen Wiedmann @ 2002-09-10 0:10 UTC (permalink / raw)
To: cygwin; +Cc: voss
Ulrich Voss wrote:
> I have a slightly different problem than everybody else after
> upgrading to the newest version of OpenSSH (3.4p1). SSHD starts
> fine and I can login as before. But I can't start another service after
> logging on the machine.
> I user SSH for tunneling VNC traffic. I have normally switched off
> vnc for various reasons and start it after logging in with "net start
> winvnc". This worked fine for months now, but after upgrading to
> OpenSSH 3.4 I get the error "System Fehler 5 aufgetreten" which
> should translate to sth. like "system error 5 has occured". I can
> start and stop winvnc from the local console fine. Only when logged
> in remote via ssh I get this error.
I can confirm the problem, no solution though. Sorry. However, I
can supply an additional piece of information.
The problem seems to be related to the NT security. On the box in
question I have two users in group administrators: One local user
and a remote user (my NT domain user). Both can stop and start
services when logged in via PCAnyWhere. The former can when logged
in via SSH, the latter cant.
Any hint welcome,
Jochen
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 4+ messages in thread
* SSHD 3.4 : cannot start a different service from the shell
@ 2002-06-28 7:07 Ulrich Voss
0 siblings, 0 replies; 4+ messages in thread
From: Ulrich Voss @ 2002-06-28 7:07 UTC (permalink / raw)
To: cygwin
Hi,
I have a slightly different problem than everybody else after
upgrading to the newest version of OpenSSH (3.4p1). SSHD starts
fine and I can login as before. But I can't start another service after
logging on the machine.
I user SSH for tunneling VNC traffic. I have normally switched off
vnc for various reasons and start it after logging in with "net start
winvnc". This worked fine for months now, but after upgrading to
OpenSSH 3.4 I get the error "System Fehler 5 aufgetreten" which
should translate to sth. like "system error 5 has occured". I can
start and stop winvnc from the local console fine. Only when logged
in remote via ssh I get this error.
Any ideas?
TIA
Ulrich.
-----------------------------------------------------------------
Ulrich Voss \ \ / /__ / ___|__ _| |
VoCal web publishing \ \ / / _ \| | / _` | |
voss@vocalweb.de \ V / (_) | |__| (_| | |
http://www.vocalweb.de \_/ \___/ \____\__,_|_|
Tel: (++49) 203-306-1560 web publishing
Fax: (++49) 203-306-1561
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-09-10 9:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-10 2:01 SSHD 3.4 : cannot start a different service from the shell Vince Hoffman
2002-09-10 3:44 ` Jochen Wiedmann
-- strict thread matches above, loose matches on Subject: below --
2002-09-10 0:10 Jochen Wiedmann
2002-06-28 7:07 Ulrich Voss
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).