Re: ssh confused about home directory?
[Answering my own question after better searching] Same question asked and answered in the thread starting https://cygwin.com/ml/cygwin/2016-06/msg00400.html. The answer is to set db_home in nsswitch.conf. Comment: the current behavior strikes me as unfortunate and surprising. From: Boylan, Ross Sent: Tuesday, February 19, 2019 11:15:47 AM To: cygwin@cygwin.com Subject: ssh confused about home directory? I recently installed cygwin on Win 10, both 64 bit. When I run ssh in a cygwin shell it complains Could not create directory '/home/rdboylan/.ssh'. The /home directory is empty--that is, it has no rdboylan subdirectory. My home directory appears to be /cygdrive/c/Users/rdboylan; that is the value of $HOME and where I end up when I do cd. As far as I can tell from the docs, having c:/Users/rdboylan as home is fine, but ssh doesn't seem to be respecting it. /etc/nsswitch.conf has no uncommented lines and /etc/passwd does not exist (both being ways to define the home directory on cygwin according to the internet). In a Windows Command Prompt %HOME% is C:\Users\rdboylan What's the most appropriate way to fix this problem? Thanks. Ross -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
ssh confused about home directory?
I recently installed cygwin on Win 10, both 64 bit. When I run ssh in a cygwin shell it complains Could not create directory '/home/rdboylan/.ssh'. The /home directory is empty--that is, it has no rdboylan subdirectory. My home directory appears to be /cygdrive/c/Users/rdboylan; that is the value of $HOME and where I end up when I do cd. As far as I can tell from the docs, having c:/Users/rdboylan as home is fine, but ssh doesn't seem to be respecting it. /etc/nsswitch.conf has no uncommented lines and /etc/passwd does not exist (both being ways to define the home directory on cygwin according to the internet). In a Windows Command Prompt %HOME% is C:\Users\rdboylan What's the most appropriate way to fix this problem? Thanks. Ross -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Programs become a no-op [SOLVED]
Thanks Marco, David and Brian for your responses. After the diagnostic steps described below, suggested by you, I ran the setup program and told it to reinstall cygwin, cygwin-base, and adwaita-icon-theme. ssh and man are working again. I'm a little puzzled how I got in this state, although it's possible I ran setup while I had a terminal open. And I wonder why the setup program didn't reinstall the damaged packages itself, or at least complain about them (though there were some complaints--see last paragraph below). Running strace ssh produced a popup "The procedure entry point __memcpy_chk could not be located in the dynamic link library cygwin1.dll" and cygcheck's output included Package Version Status _autorebase 001007-1OK Missing file: /usr/share/icons/Adwaita/icon-theme.cache from package adwaita-icon-theme adwaita-icon-theme3.26.1-1Incomplete alternatives 1.3.30c-10 OK at-spi2-core 2.26.2-1OK base-cygwin 3.8-1 OK base-files4.2-4 OK bash 4.4.12-3OK bzip2 1.0.6-3 OK ca-certificates 2.22-1 OK coreutils 8.26-2 OK csih 0.9.9-1 OK curl 7.59.0-1OK cygrunsrv 1.62-1 OK cygutils 1.4.16-2OK Missing file: /usr/bin/gencat.exe from package cygwin cygwin2.10.0-1Incomplete Those were the only 2 Incomplete packages. Finally, I've been getting errors from the post-installation that some packages were not setup, but since they all seemed to be graphical and I don't have cygwin/X installed I thought they were harmless. I guess they weren't. After the package reinstallation I get no such errors. Ross -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Programs become a no-op
I've tried ssh -V ssh --help ssh -v somene@somewhere and in all cases nothing happens except that I get a new command prompt. They used to work fine. I tried reinstalling ssh and libssh2_1. No help. I think the problem is more general: man ssh man -V man --help man man also all get nothing. On the other hand, grep, find and date (date might be a shell builtin) all seem to be working fine. I just updated; it's been at least a week since earlier updates, and it's probably longer than that since I used ssh. Running under Windows 7, 64 bit (cygwin is 64 bit too). I have local admin rights, used for the install, but did not request them when running cygwin. Symantec EndPoint Protection, though the logs don't seem to show it blocking or quarantining anything. Any ideas? Thanks. Ross Boylan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Adding font path to X server
I did see your answer, and it worked! Thanks very much. I now have a very simple .startxwinrc. I noticed the default one does a lot of stuff. Should I try to include it or copy from it? Is it getting sourced automatically anyway? It looked as if the system startxwinrc sources the user .startxwinrc, hence my thought that it might be running anyway. Ross From: cygwin-ow...@cygwin.com [cygwin-ow...@cygwin.com] on behalf of Mark Geisert [m...@maxrnd.com] Sent: Monday, March 30, 2015 9:21 PM To: cygwin@cygwin.com Subject: Re: Adding font path to X server Boylan, Ross writes: I need the Cygwin X server to have access to fonts from dosemu; currently I have to add the path manually each time I start. I thought I was following the manual by setting up .startxwinrc as xset fp+ /usr/share/fonts/dosemu xterm but startxwin fails to start (details below). How do I avoid having to set the path manually? I'd appreciate cc's as my subscription to the list is currently in an odd state, and may not be working. Sorry, no can do with the gmane ML gateway I'm using. Hope you see this on the mailing list. $ startxwin Welcome to the XWin X Server [...] xset: bad font path element (#6), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax /home/rdboylan/.startxwinrc: line 2: $'xterm\r': command not found xinit: connection to X server lost The commands in .startwinxrc work fine when typed into an xterm after X launches. You appear to have at least one CR character in your .startxwinrc file. Use d2u on the file to get rid of it/them. If that alone doesn't fix your issue, you may need to add 'xset fp rehash' after the existing 'xset' command. Be sure not to add more CR chars if you edit the file again :-) . ..mark -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Adding font path to X server
I need the Cygwin X server to have access to fonts from dosemu; currently I have to add the path manually each time I start. I thought I was following the manual by setting up .startxwinrc as xset fp+ /usr/share/fonts/dosemu xterm but startxwin fails to start (details below). How do I avoid having to set the path manually? I'd appreciate cc's as my subscription to the list is currently in an odd state, and may not be working. $ startxwin Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.17.1.0 OS: CYGWIN_NT-6.1 WIHS-1QS3PW1-DT 1.7.35(0.287/5/3) 2015-03-04 12:09 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.17.1-2 built 2015-02-23 XWin was started with the following command line: /usr/bin/XWin :0 -multiwindow -auth /home/rdboylan/.serverauth.5388 .. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. xset: bad font path element (#6), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax /home/rdboylan/.startxwinrc: line 2: $'xterm\r': command not found xinit: connection to X server lost The commands in .startwinxrc work fine when typed into an xterm after X launches. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
