On Nov 13, 2019, at 2:08, Frank Redeker wrote:
> I think on both systems the handling of 8.3 names is configured
> differently. You can check this with the Window command fsutil. (This
> command requires elevated permissions)
>
> I get the following output on my system.
>
>
I have two almost identical build servers, but cygpath is not behaving as
expected on one of them. Here is the output from the “good” build server:
$ cygpath.exe —version | head -1
cygpath (cygwin) 2.11.2
$ cygpath -d 'E:\Program Files (x86)\IAR Systems'
E:\PROGRA~1\IARSYS~1
Cygpath
If so, is there a way to install it from the command line? I need it on a
server that I usually just ssh into and running setup.exe is a little
cumbersome.
If not, what is the best/easiest way to get it? I would like to run a Perl
script on a Windows server under Cygwin that requires
On Mar 10, 2010, at 4:37, Thomas Wolff wrote:
Actually, if the file system does not support hard links, a tar
file that contains them doesn't properly extract at all, it will
rather report errors for those files.
(At least that's what it does on a network filesystem whose mount
doesn't
Here is an update from my experiments (sorry for the delay). As
Corinna explained, symlinks created in Cygwin are only recognized by
Cygwin, so what I wanted to do wasn't really possible. However, we
still wanted to be able to update the share from Windows (a GUI
application was written
On Mar 9, 2010, at 13:44, Larry Hall (Cygwin) wrote:
On 3/9/2010 10:11 AM, Alfred von Campe wrote:
The solution was to use hard links in the tar file (which doesn't
use up
any more space), and when it was untar'ed on Windows, everything
worked
^
On NTFS partitions
Real symlinks on a remote CIFS system are not recognized by Cygwin or
Windows either. Rather, they are converted to real files by the
underlying CIFS server so that dumb Windows clients don't get
confused.
Ah, that makes sense and explains some behavior I was seeing.
Symlinks created with
Do symbolic links work over CIFS? I'm having a really strange
problem with symlinks. Here is the story.
We have a small NAS box that is accessed via both NFS and CIFS. The
former is needed for the actual production access of the files on the
share, but the latter is used to update the
I have a strange problem when trying to compile a project under
Cygwin with dmake. If I start a remote desktop connection to our
Windows 2003 server, and start a Cygwin window (i.e., run
Cygwin.bat), I am able to build our project just fine. This also
works in a native CMD window.
On Apr 2, 2009, at 11:23, Corinna Vinschen wrote:
This chapter in the new Cygwin 1.7 User's Guide is supposed to
explain what's going on when switching the user context from a
service like sshd:
Thanks, Corinna, I will read this as soon as I get a chance (it's
waiting at the printer for me
On Apr 2, 2009, at 13:30, Dave Korn wrote:
Is this possibly caused by having $SHELL set in the environment
in one case
but not the other?
We have a winner! The SHELL environment variable was set in both
cases to /bin/bash. Well, doing a echo $SHELL returned /bin/bash
in both cases.
I have a strange problem when trying to compile a project under
Cygwin with dmake. If I start a remote desktop connection to our
Windows 2003 server, and start a Cygwin window (i.e., run
Cygwin.bat), I am able to build our project just fine. This also
works in a native CMD window.
rsync -rtuplg --stats --verbose --progress --modify-window=2 /
cygdrive/c/localfolder /cygdrive/z/backups/
...
...
The local and remote folders were already synchronized, that is why
0 files were transferred. File list generation did take only 3
minutes but the whole process took more than
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
On Apr 11, 2008, at 11:48, I wrote:
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.
I
On Mar 28, 2008, at 11:28, Dave Korn wrote:
Alfred von Campe wrote on 28 March 2008 12:30:
I have tried various ways to get the sshd service started as a domain
user (instead of the default local user sshd_server) and can not
get it to work. What is the correct syntax to specify a domain user
On Apr 2, 2008, at 9:27, Corinna Vinschen wrote:
Did you try anything besides switching the user? For instance:
- Did you check the event log?
Yes, did not find anything useful.
- Did you check /var/run/sshd.log? If it's empty it's probably
because
the domain user has no write
[I'm reposting this with a couple of corrections/clarifications and
also to raise its visibility since I didn't get any responses last
time :-)]
It's been a month since Larry Hall replied to my last post on this
topic (thanks, BTW), and this issue has bubbled up to the top again.
I have
On Feb 26, 2008, at 18:29, Larry Hall (Cygwin) wrote:
How did you make this change? If you removed and reinstalled the
service
with 'cygrunsrv' like the sshd configuration script does, then use the
'-W, --passwd password' flag. Otherwise, specify the password in
Control
I've read about the restrictions on accessing shares while logged
into a Windows system with the Cygwin ssh daemon. We are interested
in this to do remote builds, and it would be nice to access network
shares. We only really need one user to be able to log in, so I
thought I'd change the
A quick update on the my situation (I am the original poster). After
removing Cygwin and reinstalling it, re-running ssh-host-config, and
making the home directory in /etc/passwd a local directory (i.e., not
a network drive), I am now able to log into the Windows system from a
Linux
On Feb 7, 2008, at 9:46, Dave Korn wrote:
It all depends where you keep your home directory. For a home on
your local
HD, that's fine, but if you have home on a network share, you need
'smbntsec',
since ntsec defaults to only cover local drives for speed.
Yes, our home directories are
I have a pretty vanilla Cygwin installation on a Windows 2003 Server
(SP1) system. Yesterday, I tried to enable the sshd service by
running the ssh-host-config script. Everything appeared to work fine
and I let the script create the two recommended user accounts. I was
also able to
On Feb 6, 2008, at 9:55, Dave Korn wrote:
How do the perms on /home/av16209/.ssh/* look? How do they look
with
CYGWIN=smbntsec?
Interesting. I had CYGWIN set to binmode tty ntsec according to
some instructions I found by googling. Here are the relevant results:
bash-3.2$
If you want this enabled indelibly just for the sshd service and
you don't
want to go skulking around in the registry, you can re-run ssh-host-
config
and specify 'smbntsec' as one of the settings when it asks you what
you want
for the service. This is a good thing to do because it allows
25 matches
Mail list logo
