| delorie.com/archives/browse.cgi | search |
On Apr 2, 2008, at 9:27, Corinna Vinschen wrote: > - Did you check /var/run/sshd.log? If it's empty it's probably > because > the domain user has no write permission. > > - Does the domain user have an entry in the local /etc/passwd? sshd > needs that when checking file ownership. And it allows to > specify the > user to cygrunsrv without the "domain\win_username" syntax. > > - Did you chown /etc/ssh* and /var/empty to the domain user when > trying > to start the service under that account? That's a must have. It's taken me a while to get to this, but changing the above mentioned permissions did the trick. I can now log on and access network shares! This will make the build engineers' lives a lot easier. Thank you for a great product and for all the help on this list! Well, I spoke a little too soon. I got this working on two systems, but can not get it to work on a third. The ssh daemon appears to start (neither cygrunsrv -S nor starting it from the Services Panel gives an error), but it really does not. The Event Viewer Application log shows the following: The description for Event ID ( 0 ) in Source ( sshd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: sshd: PID 2920: service `sshd' failed: signal 11 raised. Any ideas what could be raising signal 11 (SIGSEGV) and how I would go about debugging this? ssh access was working to this machine before I changed the file system permissions and the account information for the sshd service. Alfred -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |