Cygwin infrastructure assistance, part 3

Cygwin infrastructure assistance, part 3

[Yaakov Selkowitz]

It appears that the same jobs (upset and check-cygwin-mirrors) are being 
run from both the cygwin@ and cygwin-admin@ crontabs simultaneously, 
which is causing some conflicts.  I am fairly sure that they were only 
in the latter when I started, and in any case I only have access to the 
latter.  Could someone please check these and make sure that only the 
cygwin-admin@ crontab has these?

TIA,

-- 
Yaakov Selkowitz
Associate Software Engineer, ARM
Red Hat, Inc.

Re: Cygwin infrastructure assistance, part 3

[Yaakov Selkowitz]

On 2014-08-12 00:27, Yaakov Selkowitz wrote:
> It appears that the same jobs (upset and check-cygwin-mirrors) are being
> run from both the cygwin@ and cygwin-admin@ crontabs simultaneously,
> which is causing some conflicts.  I am fairly sure that they were only
> in the latter when I started, and in any case I only have access to the
> latter.  Could someone please check these and make sure that only the
> cygwin-admin@ crontab has these?

There may also be jobs in the root crontab that are Cygwin related. 
Could someone please check this as well; we want all Cygwin-specific 
jobs in the cygwin-admin@ crontab so that we can manage them ourselves.

TIA,

-- 
Yaakov Selkowitz
Associate Software Engineer, ARM
Red Hat, Inc.

Re: Cygwin infrastructure assistance, part 3

[Frank Ch. Eigler]

Hi -

> There may also be jobs in the root crontab that are Cygwin related. 
> Could someone please check this as well; we want all Cygwin-specific 
> jobs in the cygwin-admin@ crontab so that we can manage them ourselves.

OK, commented out a few items from the root crontab, related to
cygwin/cleancache, chowning stuff under the ftp pub/cygwin directory,
and running cygwin-staging/mkpkgdir  .

- FChE

Re: Cygwin infrastructure assistance, part 3

[Christopher Faylor]

On Tue, Aug 12, 2014 at 02:29:40PM -0400, Frank Ch. Eigler wrote:
>Yaakov wrote:
>> There may also be jobs in the root crontab that are Cygwin related. 
>> Could someone please check this as well; we want all Cygwin-specific 
>> jobs in the cygwin-admin@ crontab so that we can manage them ourselves.
>
>OK, commented out a few items from the root crontab, related to
>cygwin/cleancache, chowning stuff under the ftp pub/cygwin directory,
>and running cygwin-staging/mkpkgdir  .

The cleancache and mkpkgdir could likely be run by cygwin-owned crontab
but the chown part needs to still be there.  It changes ownership and
protection for files uploaded to the cygwin release directory by people
with login privileges to sourceware who update the release area by hand.

cgf

Re: Cygwin infrastructure assistance, part 3

[Yaakov Selkowitz]

On 2014-08-12 13:29, Frank Ch. Eigler wrote:
>> There may also be jobs in the root crontab that are Cygwin related.
>> Could someone please check this as well; we want all Cygwin-specific
>> jobs in the cygwin-admin@ crontab so that we can manage them ourselves.
>
> OK, commented out a few items from the root crontab, related to
> cygwin/cleancache, chowning stuff under the ftp pub/cygwin directory,
> and running cygwin-staging/mkpkgdir  .

Could you specify what jobs you commented out, because it sounds like 
not all of those are in the cygwin-admin crontab yet.

-- 
Yaakov Selkowitz
Associate Software Engineer, ARM
Red Hat, Inc.

Re: Cygwin infrastructure assistance, part 3

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

On Aug 12 14:40, Christopher Faylor wrote:
> On Tue, Aug 12, 2014 at 02:29:40PM -0400, Frank Ch. Eigler wrote:
> >Yaakov wrote:
> >> There may also be jobs in the root crontab that are Cygwin related. 
> >> Could someone please check this as well; we want all Cygwin-specific 
> >> jobs in the cygwin-admin@ crontab so that we can manage them ourselves.
> >
> >OK, commented out a few items from the root crontab, related to
> >cygwin/cleancache, chowning stuff under the ftp pub/cygwin directory,
> >and running cygwin-staging/mkpkgdir  .
> 
> The cleancache and mkpkgdir could likely be run by cygwin-owned crontab
> but the chown part needs to still be there.  It changes ownership and
> protection for files uploaded to the cygwin release directory by people
> with login privileges to sourceware who update the release area by hand.

Could the chown be handled by some sudo magic?


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: Cygwin infrastructure assistance, part 3

[Christopher Faylor]

On Wed, Aug 13, 2014 at 03:18:02PM +0200, Corinna Vinschen wrote:
>On Aug 12 14:40, Christopher Faylor wrote:
>> On Tue, Aug 12, 2014 at 02:29:40PM -0400, Frank Ch. Eigler wrote:
>> >Yaakov wrote:
>> >> There may also be jobs in the root crontab that are Cygwin related. 
>> >> Could someone please check this as well; we want all Cygwin-specific 
>> >> jobs in the cygwin-admin@ crontab so that we can manage them ourselves.
>> >
>> >OK, commented out a few items from the root crontab, related to
>> >cygwin/cleancache, chowning stuff under the ftp pub/cygwin directory,
>> >and running cygwin-staging/mkpkgdir  .
>> 
>> The cleancache and mkpkgdir could likely be run by cygwin-owned crontab
>> but the chown part needs to still be there.  It changes ownership and
>> protection for files uploaded to the cygwin release directory by people
>> with login privileges to sourceware who update the release area by hand.
>
>Could the chown be handled by some sudo magic?

No.

cgf

Re: Cygwin infrastructure assistance, part 3

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]

On Aug 13 10:09, Christopher Faylor wrote:
> On Wed, Aug 13, 2014 at 03:18:02PM +0200, Corinna Vinschen wrote:
> >On Aug 12 14:40, Christopher Faylor wrote:
> >> On Tue, Aug 12, 2014 at 02:29:40PM -0400, Frank Ch. Eigler wrote:
> >> >Yaakov wrote:
> >> >> There may also be jobs in the root crontab that are Cygwin related. 
> >> >> Could someone please check this as well; we want all Cygwin-specific 
> >> >> jobs in the cygwin-admin@ crontab so that we can manage them ourselves.
> >> >
> >> >OK, commented out a few items from the root crontab, related to
> >> >cygwin/cleancache, chowning stuff under the ftp pub/cygwin directory,
> >> >and running cygwin-staging/mkpkgdir  .
> >> 
> >> The cleancache and mkpkgdir could likely be run by cygwin-owned crontab
> >> but the chown part needs to still be there.  It changes ownership and
> >> protection for files uploaded to the cygwin release directory by people
> >> with login privileges to sourceware who update the release area by hand.
> >
> >Could the chown be handled by some sudo magic?
> 
> No.

Why not?  Isn't that what sudo is for?  We could create a script,
owned by root, which calls chown only under a specific directory,
and the /etc/sudoers file could contain an entry

  cygwin-admin  NOPASSWD:  /path/to/script

Or is there a non-sudoers policy on sourceware?


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]