Modify

Ticket #472 (closed enhancement: fixed)

Opened 14 years ago

Last modified 10 years ago

Make POSIX.py work under Cygwin

Reported by: dclark Owned by: solj
Priority: minor Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-client Version: 1.0
Keywords: Cc:

Description

On Cygwin, there is no "root" or "UID 0" user, because the users are all taken from the Windows system. I believe the only constant is the "SYSTEM" account; I don't think the UID of "SYSTEM" is consistent however. For groups, there are both "SYSTEM" and "root"; I'm not sure which would be better to use, SYSTEM I'd guess for consistency.

I'm thinking maybe I should rollback my uid/gid normalization stuff and just make the default uid/gid hard-coded platform-specific; so the client would detect what system it's on, and do this:

OS Default User Default Group
AIX root system
Cygwin SYSTEM SYSTEM
Anything else root root

Thoughts? This would be client-side-only, unlike the current solution.

Other than this Bcfg2 seems to work fine under Cygwin (Python 2.5.1, m2crypto 0.17 build from source, bcfg2 0.9.5pre1). Of course only "Action" and "POSIX" client tools show up.

Attachments

Change History

comment:1 Changed 13 years ago by solj

  • Version set to 1.0
  • Milestone set to Bcfg2 1.0 Release

comment:2 Changed 13 years ago by solj

  • Milestone changed from Bcfg2 1.0 Release to POSIX unification

comment:3 Changed 12 years ago by solj

  • Milestone changed from POSIX unification to Bcfg2 1.0.1 Release

comment:4 Changed 12 years ago by solj

  • Milestone changed from Bcfg2 1.0.1 Release to Bcfg2 1.1.0 Release

comment:5 Changed 12 years ago by solj

  • Cc solj@… added

comment:6 follow-up: ↓ 8 Changed 12 years ago by solj

  • Owner changed from desai to solj
  • Status changed from new to accepted
  • Milestone changed from Bcfg2 1.1.0 Release to Bcfg2 1.2.0 Release

I have figured out a way to accomplish different default permissions using per-plugin info.xml files. I have an example working for Cfg (but it doesn't yet use the FileMonitor? code). Once it does, I think this is the best way to handle differing architectures.

comment:7 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.2.0 Release to Bcfg2 1.3.0 Release

comment:8 in reply to: ↑ 6 Changed 11 years ago by solj

Replying to solj:

I have figured out a way to accomplish different default permissions using per-plugin info.xml files. I have an example working for Cfg (but it doesn't yet use the FileMonitor? code). Once it does, I think this is the best way to handle differing architectures.

I'm still planning on integrating this, but the preferred way to handle different architectures is via dynamic groups using Probes. This will allow you to set differing permissions based on groups in info.xml files.

comment:9 Changed 11 years ago by solj

  • Status changed from accepted to closed
  • Resolution set to fixed

I have also tested that bcfg2 works fine under Cygwin using the latest python (2.6.5) along with the built-in ssl module. All POSIX entries types, with the exception of device work as expected.

comment:10 Changed 10 years ago by solj

  • Cc solj@… removed
  • Milestone changed from Bcfg2 1.3.0 Release to Bcfg2 1.2.0 Release

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.