As I mentioned before, I have *two* entries in /etc/passwd, one corresponding to my senior account on the local system and one corresponding to the domain account.
I've had some really strange behavior as a result. I was able to rsync from the windows box to itself only to discover that the
On Jan 6 13:07, Chris Taylor wrote:
I wonder if it would be worth having ssh-host-config set tcpip as a
dependancy for sshd on all systems? While this doesn't seem to have
cropped up much, specifically, it couldn't hurt..
I've send a patch upstream which adds a `-y tcpip' to
Ugh, top-posting... Reformatted.
On Mon, 9 Jan 2006, Ken Senior wrote:
Larry Hall (Cygwin) wrote:
Ken Senior wrote:
snip
Some packages (SSH) think the home page should be /home/senior
whereas the default bash shell thinks it's located in
/cygdrive/c/Documents and
David Christensen wrote:
Ken Senior wrote:
Does anyone know why after a Windows XP reboot one must restart the SSH
daemon in order to allow incoming ssh?
rebaseall was the cure for me:
http://sourceware.org/ml/cygwin/2005-02/msg00465.html
Installing and running rebase did
Ken Senior wrote:
snip
Some packages (SSH) think the home page should be /home/senior whereas the
default bash shell thinks it's located in /cygdrive/c/Documents and
Settings/senior.DOMAIN.
This is not surprising. You set HOME in your environment to point to
'/cygdrive/c/Documents and
Does anyone know why after a Windows XP reboot one must restart the SSH
daemon in order to allow incoming ssh? The process is automatically
running after a reboot but all incoming SSH from remote clients are
terminated with the following message being displayed on the remote
client:
Ken Senior wrote:
Does anyone know why after a Windows XP reboot one must restart the SSH
daemon in order to allow incoming ssh? The process is automatically
running after a reboot but all incoming SSH from remote clients are
terminated with the following message being displayed on the remote
Great. I have made said attachment. One interesting oddity about my
installation is that I have two usernames which are identical, one for our
Windows domain and one for the administrator account on my PC. I made
sure to give both accounts admin privileges locally on the machine, but
that seems
Ken Senior wrote:
Does anyone know why after a Windows XP reboot one must restart the SSH
daemon in order to allow incoming ssh? The process is automatically
running after a reboot but all incoming SSH from remote clients are
terminated with the following message being displayed on the
Top-posting reformatted.
Ken Senior wrote:
On Fri, Jan 6, 2006, Chris Taylor [EMAIL PROTECTED] said:
http://cygwin.com/acronyms/#PCYMTNQREAIYR
Ken Senior wrote:
Does anyone know why after a Windows XP reboot one must restart
the SSH daemon in order to allow incoming ssh? The process
Brian Dessent wrote:
Ken Senior wrote:
Does anyone know why after a Windows XP reboot one must restart the SSH
daemon in order to allow incoming ssh? The process is automatically
running after a reboot but all incoming SSH from remote clients are
terminated with the following message being
On Fri, 6 Jan 2006, Chris Taylor wrote:
Brian Dessent wrote:
Ken Senior wrote:
Does anyone know why after a Windows XP reboot one must restart the
SSH daemon in order to allow incoming ssh? The process is
automatically running after a reboot but all incoming SSH from
remote
I wonder if it would be worth having ssh-host-config set tcpip as a
dependancy for sshd on all systems? While this doesn't seem to have
cropped up much, specifically, it couldn't hurt..
This has been discussed before, see
http://cygwin.com/ml/cygwin/2005-12/msg00089.html. I guess it's
Brett Serkez wrote:
I wonder if it would be worth having ssh-host-config set tcpip as a
dependancy for sshd on all systems? While this doesn't seem to have
cropped up much, specifically, it couldn't hurt..
This has been discussed before, see
http://cygwin.com/ml/cygwin/2005-12/msg00089.html.
Ken Senior wrote:
Does anyone know why after a Windows XP reboot one must restart the SSH
daemon in order to allow incoming ssh?
rebaseall was the cure for me:
http://sourceware.org/ml/cygwin/2005-02/msg00465.html
One interesting oddity about my installation is that I have two
15 matches
Mail list logo
