Re: Permission Problems

On Mon, Apr 25, 2016 at 12:09 AM, Marco Atzeri wrote: > On 25/04/2016 02:29, Dave Caswell wrote: >> >> This is a followup to: https://cygwin.com/ml/cygwin/2016-03/msg00345.html >> >> To recap, making three nested directories on a non-C drive produces a >> third level which is unusable. >> >> dave

Re: Permission Problems

On Mon, Apr 25, 2016 at 4:30 AM, Tatsuro MATSUOKA wrote: >> From: Dave Caswell >> To: cygwin >> Cc: >> Date: 2016/4/25, Mon 09:29 >> Subject: Permission Problems >> >>T his is a followup to: https://cygwin.com/ml/cygwin/2016-03/msg00345.html >> >> To recap, making three nested director

Re: Permission Problems

> From: Dave Caswell  > To: cygwin    > Cc: > Date: 2016/4/25, Mon 09:29 > Subject: Permission Problems > >T his is a followup to: https://cygwin.com/ml/cygwin/2016-03/msg00345.html > > To recap, making three nested directories  on a non-C drive produces a > third level which is unusable

Re: Permission Problems

On 25/04/2016 02:29, Dave Caswell wrote: This is a followup to: https://cygwin.com/ml/cygwin/2016-03/msg00345.html To recap, making three nested directories on a non-C drive produces a third level which is unusable. davec@MERCURYWIN ~/python $ rm -rf g1 davec@MERCURYWIN ~/python $ mkdir g1 g1/

Re: CSIH csih_get_cygenv function (was Re: permission problems with ssh-host-config)

On Jan 28 10:17, Charles Wilson wrote: > Corinna Vinschen wrote: > > What I'm planning to do is this: > > > > - In cygwin-service-installation-helper.sh I would like to drop the > > check for the content of CYGWIN entirely. > > OK. Fine. I'll apply a patch at one point today. > > - In ssh-ho

Re: CSIH csih_get_cygenv function (was Re: permission problems with ssh-host-config)

Corinna Vinschen wrote: > What was the exact reason to restrict the input for the CYGWIN settings > in csih? I don't quite understand why a lot of options are disallowed > at all, for instance "winsymlinks", "ntea", etc. Inherited from pre-existing code (either old ssh-*-config or exim-config).

Re: CSIH csih_get_cygenv function (was Re: permission problems with ssh-host-config)

On Jan 28 12:21, Corinna Vinschen wrote: > What I'm planning to do is this: > > - In cygwin-service-installation-helper.sh I would like to drop the > check for the content of CYGWIN entirely. > > - In ssh-host-config I'd like to set the default for the CYGWIN settings > to an empty string.

CSIH csih_get_cygenv function (was Re: permission problems with ssh-host-config)

Hi Chuck, On Jan 28 11:19, Corinna Vinschen wrote: > On Jan 27 19:35, Siegmar Gross wrote: > > *** Info: Note that the CYGWIN variable must contain at least "ntsec" > > *** Info: for sshd to be able to change user context without password. > > *** Query: Enter the value of CYGWIN for the daemon: [

Re: permission problems with ssh-host-config

On Jan 27 19:35, Siegmar Gross wrote: > *** Info: Note that the CYGWIN variable must contain at least "ntsec" > *** Info: for sshd to be able to change user context without password. > *** Query: Enter the value of CYGWIN for the daemon: [ntsec] ntsec tty server > *** ERROR: Only [no] "check_case:s

Re: permission problems with ssh-host-config

On Tue, Jan 27, 2009 at 07:35:44PM +0100, Siegmar Gross wrote: >Why doesn't the script allow the values "ntsec tty server" for CYGWIN >any longer although "cygserver" needs "server" in CYGWIN? Presumably because sshd doesn't need server and it certainly doesn't need "tty". cgf -- Unsubscribe inf

Re: permission problems (and more)

At 01:08 AM 5/6/2004, you wrote: >--- "Larry Hall (RFK Partners, Inc)" wrote: >> From a comparison of your environment with mine, >> I see that you don't give specific permissions to > >Just when I thought I would get the answer, it >looks like you didn't pay your internet bill or >something (your

Re: permission problems (and more)

--- "Larry Hall (RFK Partners, Inc)" wrote: > From a comparison of your environment with mine, > I see that you don't give specific permissions to Just when I thought I would get the answer, it looks like you didn't pay your internet bill or something (your answer ends in the middle of the sentenc

Re: permission problems (and more)

At 10:51 PM 5/5/2004, you wrote: >--- Larry Hall wrote: >> OK, first check the output of /var/log/cron.log. >> If that doesn't clarify the situation for you, send >> it and the output of 'ls -Rl /var' to the list. > >$ ls -Ral /var >/var: >total 0 >drwxr-x---+ 3 user Users 0 Thu Mar

Re: permission problems (and more)

--- Larry Hall wrote: > OK, first check the output of /var/log/cron.log. > If that doesn't clarify the situation for you, send > it and the output of 'ls -Rl /var' to the list. $ ls -Ral /var /var: total 0 drwxr-x---+ 3 user Users 0 Thu Mar 25 18:43:15 2004 cache/ drwxrwxrwt+ 3 u

Re: permission problems (and more)

At 05:24 PM 4/26/2004, you wrote: >--- Larry Hall wrote: >> At 04:43 PM 4/14/2004, you wrote: >> >The cron service failed to start due to the following error: >> >Access is denied. >> >> > >OK, let's just start with cron (ignoring the ssh >p

Re: permission problems (and more)

--- Larry Hall wrote: > At 04:43 PM 4/14/2004, you wrote: > >The cron service failed to start due to the following error: > >Access is denied. > > OK, let's just start with cron (ignoring the ssh problem for the moment. $ ./cron_diagnose.s

Re: permission problems (and more)

At 04:43 PM 4/14/2004, you wrote: >Running cygwin (on Windows 2000) for a few months, and >finally decided that I wanted sshd and cron activated. > >Logged on as administrator and did: > >cron: >cygrunsrv -I cron -p /bin/cron -a -D > >sshd: >run the ssh-host-config script and answer the questions (

Re: Permission problems with recent Cygwin

[EMAIL PROTECTED] wrote: > > (Sorry this took so long; it's taken me days to find the hours required > to investigate.) Hi Luke, it would take me days to fully analyze your problem, but you seem to have realized what I was going to tell you urgently: ntsec is now on by default. To turn off ntse

Re: Permission problems with recent Cygwin

(Sorry this took so long; it's taken me days to find the hours required to investigate.) I've got some more info, below, and have also read through all the permissions threads on the cygwin mailing list I could find, and to read about half the ntsec threads over the last year or so. I don't think

Re: Permission problems with recent Cygwin

Hmmm. I recently had need of reinstalling my cygwin installation. I did find the permissions were overly restrictive. Even though I had marked the installation for everyone, only the account I used to create it could login until I did: chmod -R ug+rwX,o+rX / chmod 1777 `find / -n

Re: Permission problems with recent Cygwin

On Wed, Jul 16, 2003 at 11:37:19AM +1000, [EMAIL PROTECTED] wrote: > On some recent installs of Cygwin (from a snapshot of a mirror site > about a week ago), we've started getting some odd problems. Re-running > setup pointing it at a fresh setup and mirror does not fix the problems > (naturally e