> That's not what I'm seeing when I run your test program on Linux:
>
> $ ./sun
> fstat mode = 140666
> stat mode = 140777
True, but it creates the socket file with exactly how umask(0) told it to,
and stat() shows that. So yeah, I should retract that it works on Linux with
fchmod() -- on Linux
Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]!
>> what your test program was actually doing. But you seem to be assuming that
>> calling fchmod on a socket descriptor should affect the permissions on the
>> socket file (assuming the socket is bound). Is that documented anywhere?
>> POSIX
>>
On 7/2/2022 3:37 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
what your test program was actually doing. But you seem to be assuming that
calling fchmod on a socket descriptor should affect the permissions on the
socket file (assuming the socket is bound). Is that documented anywhere? POSIX
> what your test program was actually doing. But you seem to be assuming that
> calling fchmod on a socket descriptor should affect the permissions on the
> socket file (assuming the socket is bound). Is that documented anywhere?
> POSIX
> says that the behavior of fchmod on a socket descriptor
On 7/2/2022 12:16 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
I forgot to mention that my "umask" is the standard 022...
The man page says that for directories with the ACLs, it is ignored.
So in my code bind() wouldn't have created the socket with 0777, and
that's fine! Which is why I cal
I forgot to mention that my "umask" is the standard 022...
The man page says that for directories with the ACLs, it is ignored.
So in my code bind() wouldn't have created the socket with 0777, and
that's fine! Which is why I call fchmod() to fix the permissions up,
and THAT does not work. BTW,
On 7/1/2022 11:23 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
That way I'm sure I won't have any surprises with permissions when working in
/cygdrive/g/cygwin. Do you want to try that and see if it makes a difference?
I have no problems with /cygdrive/g/cygwin -- my socket file gets create
> That way I'm sure I won't have any surprises with permissions when working in
> /cygdrive/g/cygwin. Do you want to try that and see if it makes a difference?
I have no problems with /cygdrive/g/cygwin -- my socket file gets created there
with proper
permissions and reported so, too (both fstat
On 7/1/2022 6:11 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Cygwin does not do this on a standard installation. Is it something you've done
I did use the standard Setup and nothing else... My $HOME looks fine, too:
$ cd
$ pwd
/home/ANTON
$ getfacl .
# file: .
# owner: ANTON
# group: Non
> Cygwin does not do this on a standard installation. Is it something you've
> done
I did use the standard Setup and nothing else... My $HOME looks fine, too:
$ cd
$ pwd
/home/ANTON
$ getfacl .
# file: .
# owner: ANTON
# group: None
user::rwx
group::---
other::---
default:user::rwx
default:gro
On 7/1/2022 2:00 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Lastly, I forgot to list all the involved directories as they look from under
Cygwin with their permissions,
if that's of any help:
$ ls -ld ~ ~/.socket ~/subdir ~/subdir/.socket
drwx--+ 1 ANTON None 0 Jul 1 13:36 /home/ANTON
On 7/1/2022 2:00 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
getfacl does not work even for the .socket "file" in my home directory for
which ~/sun works perfectly fine with permissions
(and all subdirectories crated with mkdir under it).
Also like I said, ~/sun also works perfectly fine in
getfacl does not work even for the .socket "file" in my home directory for
which ~/sun works perfectly fine with permissions
(and all subdirectories crated with mkdir under it).
Also like I said, ~/sun also works perfectly fine in /cygdrive/g/cygwin/ but
not if I created a subdirectory with the
On 7/1/2022 1:46 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
Now, if I run this code in my Cygwin home directory (and any directory that I create
using "mkdir..." under it),
I am getting the expected results:
$ ~/sun
fstat mode = 140666
stat mode = 140666
$ ls -l .socket
srw-rw-
Hi all,
I am having an issue with socket file permissions...
So here's a mockup of code that shows the problem:
$ cat sun.c
#include
#include
#include
#include
#include
#include
#include
#define SOCKET "./.socket"
int main()
{
struct sockaddr_un addr;
On Apr 22 09:25, Achim Gratz wrote:
> Achim Gratz writes:
> >> I don't understand what you're trying to say here. Are there
> >> differences or not?
> >
> > You're on to something. I have over 500 groups in my token in the old
> > domain, but only half of those end up in the token when I'm logged
Achim Gratz writes:
>> I don't understand what you're trying to say here. Are there
>> differences or not?
>
> You're on to something. I have over 500 groups in my token in the old
> domain, but only half of those end up in the token when I'm logged in on
> the machine in the new domain (at least
Corinna Vinschen writes:
> It's dirt easy:
For you... :-) I know next to nothing about all this stuff.
> Ok. However, MSDN explicitely suggests to fetch the AuthZ context
> from the current user token, if the idea is to ask for the permissions
> of the current user. It's much less costly than
On Apr 12 21:16, Achim Gratz wrote:
> Corinna Vinschen writes:
> > I inspected the source code which handles this kind of thing. What it
> > does is to ask Windows for permissions of SID X on file Y, using AuthZ.
>
> That seems to be working correctly. For all old domain SID I've looked
> at, th
Corinna Vinschen writes:
> I inspected the source code which handles this kind of thing. What it
> does is to ask Windows for permissions of SID X on file Y, using AuthZ.
That seems to be working correctly. For all old domain SID I've looked
at, they've been prefixed by 0x7FFF when seen by t
On Apr 12 09:56, Csaba Raduly wrote:
> On 4/12/18, Corinna Vinschen wrote:
> > See sec_acl.cc, line 1127ff. This calls a function
> > authz_get_user_attribute which in turn calls a method
> > authz_ctx::get_user_attribute, sec_helper.cc, line 811ff.
>
> Ouch. Are there so many lines that you have
On 4/12/18, Corinna Vinschen wrote:
> See sec_acl.cc, line 1127ff. This calls a function
> authz_get_user_attribute which in turn calls a method
> authz_ctx::get_user_attribute, sec_helper.cc, line 811ff.
Ouch. Are there so many lines that you have to use hexadecimal notation ?
Csaba
--
You can
On Apr 11 19:17, Achim Gratz wrote:
> Corinna Vinschen writes:
> > This is a bit low on detail. What does icacls say about this file? How
> > does getfacl report the ACL on a machine in the old domain? What does
> > ls -l report on the file on both machines? Does an strace on getfacl
> > report
Corinna Vinschen writes:
> This is a bit low on detail. What does icacls say about this file? How
> does getfacl report the ACL on a machine in the old domain? What does
> ls -l report on the file on both machines? Does an strace on getfacl
> report an error in ACL checking?
There is absolutel
On Apr 11 09:03, Corinna Vinschen wrote:
> Same here, belong on the Cygwin ML. Redirecting.
>
> Corinna
>
> On Apr 10 18:47, Achim Gratz wrote:
> >
> > We're in the midst of switching to a different LDAP domain
> > organisation. All my accounts still arein the old domain and that leads
> > to
Same here, belong on the Cygwin ML. Redirecting.
Corinna
On Apr 10 18:47, Achim Gratz wrote:
>
> We're in the midst of switching to a different LDAP domain
> organisation. All my accounts still arein the old domain and that leads
> to problems when lookking at shares from a mchine in the new d
On Tue, Aug 23, 2016 at 10:23 AM, Eliot Moss wrote:
> Thank you, Erik -- you answered better than I could have! I don't
> use a domain login, so the fact that my local SID is different has
> been very plain to me!
Multiple years as a network admin managing Windows/Linux/UNIX hybrid
environments
On 8/23/2016 9:41 AM, Erik Soderquist wrote:
On Mon, Aug 22, 2016 at 3:59 AM, Björn Kautler wrote:
Your domain user SID will remain the same, however, all of the local
machine's domain SIDs will be different as it is a different host on
the domain, so I would expect permissions problems for a
On Mon, Aug 22, 2016 at 3:59 AM, Björn Kautler wrote:
> Hi Eliot,
>
> thanks for your answer.
>
> It seems this was an issue with the NTFS permissions.
> I also was not able to access the folders via Windows Explorer.
> After also fixing the Windows permissions it works now as expected so far.
>
>
Hi Eliot,
thanks for your answer.
It seems this was an issue with the NTFS permissions.
I also was not able to access the folders via Windows Explorer.
After also fixing the Windows permissions it works now as expected so far.
Do you really think I got a new SID on the new box when logging in
wi
On 8/19/2016 8:27 AM, Björn Kautler wrote:
Hi,
I have a problem I hope you can help me to solve.
I switched to a new box at work and copied over my whole cygwin folder via
rsync from the old box to the new one.
But now if I do "touch tmp", the file gets 060 permissions and not 644 like
before.
T
Hi,
I have a problem I hope you can help me to solve.
I switched to a new box at work and copied over my whole cygwin folder via
rsync from the old box to the new one.
But now if I do "touch tmp", the file gets 060 permissions and not 644 like
before.
This is very disturbing, as not even "cat <
tree as needed,
and recursively reset
all Windows file permissions all the way down. When I then rsync the USB drive
back to my user
directories, the UNIX permissions of every file are now set to executable.
This has the unfortunate
effect of granting execute permission on every file restored
Windows file permissions all the way down. When I
then rsync the USB drive back to my user directories, the UNIX
permissions of every file are now set to executable. This has the
unfortunate effect of granting execute permission on every file
restored, even those that are not executable. I
On 06/02/2015 10:53 AM, Duane Ellis wrote:
[paraphrased, and edited]
(Duane) describing the problem
(Barry) .. click click click right click .. click click to undo this crazyness
(steve) DO not do this .. you can break things in really bad ways
I would agree, I did not have time to reply yet
[paraphrased, and edited]
(Duane) describing the problem
(Barry) .. click click click right click .. click click to undo this crazyness
(steve) DO not do this .. you can break things in really bad ways
I would agree, I did not have time to reply yet.
My comment would be this:
This is
Yaakov Selkowitz sent the following at Tuesday, June 02, 2015 3:01 AM
>On Mon, 2015-06-01 at 19:01 -0500, Steven Penny wrote:
>> On Mon, Jun 1, 2015 at 1:38 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>> For goodness sake, do not do this. Do not break your computer because Cygwin
>> sucks at permi
On Mon, 2015-06-01 at 19:01 -0500, Steven Penny wrote:
> On Mon, Jun 1, 2015 at 1:38 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> > - Right click and select "Properties".
> > - Go to the "Security" tab.
> > - "Advanced".
>
> For goodness sake, do not do this. Do not break your computer because C
On Mon, Jun 1, 2015 at 1:38 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> - Right click and select "Properties".
> - Go to the "Security" tab.
> - "Advanced".
For goodness sake, do not do this. Do not break your computer because Cygwin
sucks at permissions. Just read my post on noacl and live wit
Duane Ellis sent the following at Sunday, May 24, 2015 11:03 AM
>(Sorry I cannot reply directly to the previous email I just subscribed
>to the list, I am quoting from the list archive)
>>> (from the archive - permissions inside and outside of /cygwin get messed up)
>
>I think this is *THE* cause o
(Sorry I cannot reply directly to the previous email I just subscribed to the
list, I am quoting from the list archive)
>> (from the archive - permissions inside and outside of /cygwin get messed up)
I think this is *THE* cause of my problems.
My question is how do I turn this of 100% totally -
On Thu, May 21, 2015 at 7:33 AM, DeTracey, Brendan wrote:
> $ touch /cygdrive/c/Temp/testfile
> $ ll /cygdrive/c/Temp/testfile
> -rw-rwxr--+ 1 detraceyb Domain Users 0 May 21 09:23 /cygdrive/c/Temp/testfile*
What you are seeing is the current behavior, some discussion is being had about
what is ri
Is the normal Cygwin behaviour to assign different file permissions outside of
the Cygwin root directory?
e.g.
$ touch /home/detraceyb/testfile
$ ll /home/detraceyb/testfile
-rw-r--r-- 1 detraceyb Domain Users 0 May 21 09:20 /home/detraceyb/testfile
$ getfacl /home/detraceyb/testfile
# file
Replying to myself on this topic in case anyone else is interested.
> 2) how can I get SSH to believe the two "admin" groups on my
> files are acceptable. I'm not optimistic I'm going to get SSH to
> change it's behavior so I may need to recompile it to avoid the
> check which is obviously no
Greetings, Bryan Berns!
>> He's talking about "Administrators" the SID (group).
> Interesting. Given the built-in Administrators group doesn't often
> [directly] play into permissions on remote systems or cross-system
> permission models, I'm not sure where he was going with that.
> Regardless,
> He's talking about "Administrators" the SID (group).
Interesting. Given the built-in Administrators group doesn't often
[directly] play into permissions on remote systems or cross-system
permission models, I'm not sure where he was going with that.
Regardless, I'll consider it water under the b
Bryan Berns writes:
> In the real world in large corporations with focus on security,
> "Administrators" is typically a tiered or least privilege arrangement.
He's talking about "Administrators" the SID (group).
In any case, I'd start with a throwaway share (or save the permissions
with subinacl
Andrey,
>> In the particular case of SSH, is there any way to make SSH ignore
>> these permissions?
> Thanks, I laughed.
Thanks for the less-than-helpful response. A "no" would have sufficed
if that is indeed the case.
>> and obviously
>> causing us pain given the permission weirdness. Removi
Greetings, Bryan Berns!
> I'll try to reproduce the issue on a standard NTFS volume -- although
> I would image Cygwin is just decoding the same DACL that ICACLS is
> returning. The other oddity is why it's not recognizing *me* as
> having any permissions.
getfacl may shed additional light.
> I
I'll try to reproduce the issue on a standard NTFS volume -- although
I would image Cygwin is just decoding the same DACL that ICACLS is
returning. The other oddity is why it's not recognizing *me* as
having any permissions.
In the particular case of SSH, is there any way to make SSH ignore
these
Greetings, Bryan Berns!
> Sorry for not being more clear -- yes, I had read the FAQ on SSH. I
> was taking the problem up a level to the more obvious weirdness
> demonstrated by the resultant files on a simple "touch". Why would
> Cygwin report that 'Domain Users' --- a group not in the DACL at
Andrey,
Sorry for not being more clear -- yes, I had read the FAQ on SSH. I
was taking the problem up a level to the more obvious weirdness
demonstrated by the resultant files on a simple "touch". Why would
Cygwin report that 'Domain Users' --- a group not in the DACL at all
--- as being able to
Greetings, Bryan Berns!
> I finally am moving my user community to Cygwin 1.7.35 at work and
> having some issues with ssh not thinking user's ssh keys are owned by
> the user. I indeed can see that their directory listings do not show
> their userid as having read,write, or execute to *any* of t
I finally am moving my user community to Cygwin 1.7.35 at work and
having some issues with ssh not thinking user's ssh keys are owned by
the user. I indeed can see that their directory listings do not show
their userid as having read,write, or execute to *any* of their files.
In short, just wante
o allow for Windows-security
compatibility). For a while I was able to get around the problem
with ACL's, but these days, more apps are becoming ACL-aware.
Maybe linux needs a new Discretionary-access security module, dup'ed
off the current model, but with an extra set of dummy file permissions
On Mar 23 09:57, Martin Koeppe wrote:
>
> Hi all,
>
> I just updated from cygwin 1.7.32 to 1.7.35,
> and now file permissions are calculated differently,
> which breaks fetchmail for me:
>
> Here are the Windows permissions:
> (no permissions for Domain Users / Dom
Hi all,
I just updated from cygwin 1.7.32 to 1.7.35,
and now file permissions are calculated differently,
which breaks fetchmail for me:
Here are the Windows permissions:
(no permissions for Domain Users / Domänen-Benutzer)
$ cacls fetchmailrc.txt
D:\fetchmail\fetchmailrc.txt NT-AUTORIT.T
On Mar 20 21:15, Rexdf wrote:
> > i have been using cygwin for many years and currently most of my
> > systems are at 1.7.32(0.274/5/3).
> > i had to get an update to cygwin/X which forced me to also update
> > cygwin. with the update, nearly all windows files have the permission
> > setting of 070
>
> You may have misread the original question (and its subject): the POSIX
> permissions are 070, not (0)700. These files are accessible to one or more
> of the groups the owner is a member of, but not to the owner.
>
I know clear about 070 and 700 and 0700. It is typos. That is why I
ask you to
Hi,
You may have misread the original question (and its subject): the POSIX
permissions are 070, not (0)700. These files are accessible to one or
more of the groups the owner is a member of, but not to the owner.
+1 for the ICACLS workaround though. I was bit by this recently when
setting
> i have been using cygwin for many years and currently most of my
> systems are at 1.7.32(0.274/5/3).
> i had to get an update to cygwin/X which forced me to also update
> cygwin. with the update, nearly all windows files have the permission
> setting of 070 (---rwx---) even when the file is owned
i have been using cygwin for many years and currently most of my
systems are at 1.7.32(0.274/5/3).
i had to get an update to cygwin/X which forced me to also update
cygwin. with the update, nearly all windows files have the permission
setting of 070 (---rwx---) even when the file is owned by me, an
Greetings, Will Parsons!
> I've been using Cygwin for some time now, but recently decided to try
> a parallel installation of Cygwin 64 on the same machine. I've
> noticed a strange discrepancy between how Cygwin 32 & 64 report file
> permissions:
> (32-bit)
>
I've been using Cygwin for some time now, but recently decided to try
a parallel installation of Cygwin 64 on the same machine. I've
noticed a strange discrepancy between how Cygwin 32 & 64 report file
permissions:
(32-bit)
% uname -a
CYGWIN_NT-6.1-WOW sothis 1.7.35(0.287/5/3) 20
On Feb 9 22:50, diod lightbulb wrote:
> On 9 February 2015 at 21:28, Thomas Wolff wrote:
> > Am 09.02.2015 um 16:37 schrieb diod lightbulb:
> >>
> >> ...
> >>
> >> 1- For pre-existing files/directories under /cygdrive/d and /cygdrive/e
> >>
On Feb 9 22:00, diod lightbulb wrote:
> However, I'd like to ask somthing else, is there a way to make newly
> created files outside my home to respect my umask? I just tried touch
> still buggy; ll stillbuggy reports -rw-rwxr--+ while stat -c " %a %u
> %g" stillbuggy gives back " stillbuggy
Greetings, diod lightbulb!
> All I can do now is apparently to run all my pre-existing files thru
> setfacl -b (I like to keep my files with 644 permissions) followed by
> chmod. I just have to figure out how to retain the execution bit for
> the few select executables that need it.
> However, I'
On 9 February 2015 at 21:28, Thomas Wolff wrote:
> Am 09.02.2015 um 16:37 schrieb diod lightbulb:
>>
>> ...
>>
>> 1- For pre-existing files/directories under /cygdrive/d and /cygdrive/e
>> All my file permissions that were correctly reported by ls -l as
>&g
lot of troubles subscribing to the mailing list, your answer was
already there.Thank you, this answer is spot on.
To sum up (please correct me if I'm wrong), here is how I understand
what happened:
a- the Posix file permissions under my home directory remained pretty
much the same as those files/
Am 09.02.2015 um 16:37 schrieb diod lightbulb:
...
1- For pre-existing files/directories under /cygdrive/d and /cygdrive/e
All my file permissions that were correctly reported by ls -l as
rw-r--r-- became all of a sudden -rw-rwxr--+ ??? The same for
directories where all previously 755 dirs
On Feb 9 16:37, diod lightbulb wrote:
> HI all,
>
> Maybe this is a regression. This is linked to the problem reported in
> this other thread https://cygwin.com/ml/cygwin/2015-02/msg00100.html .
> I took notice of
> it right after I updated cygwin (setup.exe 2.867) today.
Does https://cygwin.com
just saw today that it is obsolete by now (I also tried setting acl in
/etc/fstab but it didn't change the weird behavior described below).
1- For pre-existing files/directories under /cygdrive/d and /cygdrive/e
All my file permissions that were correctly reported by ls -l as
rw-r--r-- becam
Charles Plager writes:
> * Anybody else experience files that lose all permissions? Any
> suggestions on resetting the file (short of reformatting the drive)?
Ahem. Yes, that has happened once to me. I don't know how the IT guys
fixed it exactly, but they eventually deleted that file without
f
On Mar 11 08:40, Charles Plager wrote:
> Hi Andrey,
>
> I understand that Cygwin is emulating POSIX permissions (and, yes, we
> already turn this off using the /etc/fstab). What I don't understand
> is why it uses "special" permissions and not the standard "read/write"
> options that are availabl
Hi Andrey,
I understand that Cygwin is emulating POSIX permissions (and, yes, we
already turn this off using the /etc/fstab). What I don't understand
is why it uses "special" permissions and not the standard "read/write"
options that are available.
One possibility I just though of: Cygwin uses s
Greetings, Charles Plager!
> Short version: When writing to network drives (and probably local
> ones) as Cygwin is setup by default, we see the permissions being set
> using the ACLs where "creator owner" is given "full control" and
> "creator" group are given "read/execute", but by setting "spe
Hi,
Short version: When writing to network drives (and probably local
ones) as Cygwin is setup by default, we see the permissions being set
using the ACLs where "creator owner" is given "full control" and
"creator" group are given "read/execute", but by setting "special
permissions" instead of ju
file
permissions according
to POSIX from the parent file. Then the copy gets the same unuseable
permissions,
but this time for real (that is: Windows agrees that they should not
be readable!)
Windows allows you to traverse directories you don't have access to by
default.
--
Hi Corinna,
you seem to have hit the right spot. The parent directories had the
permission --
according to Cygwin, but I could still enter them via cd. Things go
wrong if under Cygwin
a file gets _copied_ via cp or something similar that takes the file
permissions according
to POSIX from the
On Jun 21 14:38, Arjen Markus wrote:
> I noticed that if I use noacl, then I get the correct looking POSIX
> permissions,
> but the Windows permissions make it impossible to use the file.
I always use "acl" as mount option.
> Try: cat gnulliver.h
$ pwd
/home/corinna/tmp/cmake/work
$ cat s
I noticed that if I use noacl, then I get the correct looking POSIX permissions,
but the Windows permissions make it impossible to use the file.
Try: cat gnulliver.h
I have had the same problem with a package built via autotools, so it
is more general
than CMake. (I first reported this on the CMa
On Jun 21 14:18, Arjen Markus wrote:
> Oops, my mistake. The correct invocation of CMake is:
>
> cmake -G "Unix Makefiles" ../
>
> (These generators are part of CMake, not of the tar file)
Ok, thank you. I never used cmake before so I didn't notice.
Other than that, I have not the problem you'
Oops, my mistake. The correct invocation of CMake is:
cmake -G "Unix Makefiles" ../
(These generators are part of CMake, not of the tar file)
Regards,
Arjen
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cyg
On Jun 21 13:40, Arjen Markus wrote:
> Here it is.
>
> Regards,
>
> Arjen
Is the tar file broken?
$ tar xvzf problem-cygwin.tgz
src/
src/CMakeLists.txt
src/include/
src/include/CMakeLists.txt
src/include/gnulliver.h.in
CMakeLists.txt
tar: A lone zero block at 11
$ mkdir work
Here it is.
Regards,
Arjen
problem-cygwin.tgz
Description: GNU Zip compressed data
--
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-
rk in
> CMakeLists.txt - the main CMake file
>
> - Run CMake in the work directory:
>
> cmake -G "Cygwin Makefiles" ../src
>
> This should complete without problems.
>
> - Examine the contents of the directory src/include in the working direc
directory:
cmake -G "Cygwin Makefiles" ../src
This should complete without problems.
- Examine the contents of the directory src/include in the working directory.
The file permissions for the file "gnulliver.h" are -
This is the result on my machine:
$ ls -l
total 13
Well, I got a message back about using too many keywords that made it look like
an off-topic reply. But without an indication (of course) of what
these keywords are.
Regards,
Arjen
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentati
On Jun 21 13:00, Arjen Markus wrote:
> I have a small testcase, but my replies are consistently refused.
> How do I solve that?
The reason should be given in the reply you get. Basically, don't
use raw email addresses in your body, don't use html.
Corinna
--
Corinna Vinschen
I have a small testcase, but my replies are consistently refused.
How do I solve that?
Regards,
Arjen
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.co
On Jun 21 10:05, Arjen Markus wrote:
> Hello,
>
> I have been experiencing problems with building several unrelated
> projects on Cygwin/Windows 7. One of them is GCC 4.8.1, another is a
> project that uses CMake to create the Makefiles. The problems occur
> either during the configuration
> (the
Hello,
I have been experiencing problems with building several unrelated
projects on Cygwin/Windows 7. One of them is GCC 4.8.1, another is a
project that uses CMake to create the Makefiles. The problems occur
either during the configuration
(the CMake-based project) or during the make itself (GCC
Greetings, Henry S. Thompson!
>> HST wrote:
>>> . . . [IIS and file access]
>>> Any suggestions?
>>
>> Only one: If you intend to mix Cygwin tools with native Windows environment,
>> let Windows handle filesystem permissions.
>> Or you will never stop running into these issues over and over again
Andrey Repin writes:
> HST wrote:
>> . . . [IIS and file access]
>> Any suggestions?
>
> Only one: If you intend to mix Cygwin tools with native Windows environment,
> let Windows handle filesystem permissions.
> Or you will never stop running into these issues over and over again.
Fair point.
On Dec 2 20:42, Henry S. Thompson wrote:
> I've spent the last hour trying to find the answer to this on the
> Web/in the archives, sorry if it's an FAQ:
>
> What's the least 'open' way possible using chgrp and chmod g+r to
> allow my IIS server to 'see' files on my local disk? At the moment I
>
Greetings, Henry S. Thompson!
> I've spent the last hour trying to find the answer to this on the
> Web/in the archives, sorry if it's an FAQ:
> What's the least 'open' way possible using chgrp and chmod g+r to
> allow my IIS server to 'see' files on my local disk? At the moment I
> have found o
I've spent the last hour trying to find the answer to this on the
Web/in the archives, sorry if it's an FAQ:
What's the least 'open' way possible using chgrp and chmod g+r to
allow my IIS server to 'see' files on my local disk? At the moment I
have found only three ways to let IIS see a file at a
On 3/14/2012 9:32 AM, James Adams wrote:
I cannot change the permissions on files when I run Hadoop in Cygwin:
java.io.IOException: Failed to set permissions of path:
\tmp\hadoop-James\mapred\staging\James-1143336710\.staging to 0700
From what I've gathered you can't really run Cygwin as
I cannot change the permissions on files when I run Hadoop in Cygwin:
java.io.IOException: Failed to set permissions of path:
\tmp\hadoop-James\mapred\staging\James-1143336710\.staging to 0700
>From what I've gathered you can't really run Cygwin as root since
Windows doesn't really have a not
On 2/16/2012 5:50 AM, Tom Quarendon wrote:
I am a member of the local administrators.
It actually sounds like noacl is what we would want here. We are just
using Cygwin shell as a basis for our build environment for ease of
portability, but we're using Visual Studio etc, not building Cygwin
execu
1 - 100 of 281 matches
Mail list logo