help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A good location for flag files & on-demand per-user apps


From: Tim Nelson
Subject: Re: A good location for flag files & on-demand per-user apps
Date: Wed, 19 Oct 2005 12:32:15 +1000 (EST)

On Thu, 13 Oct 2005, Jason Edgecombe wrote:

Hello again,

Is there a good location in the cfengine directory tree or somewhere else to put flag files? I looking to set up two sets of flags, permanent and semi-permanent. Permanent flags would be ones that specify which department a machine is in. Semi-permanent flags would be tidy'ed after some time.

I'm using a skeleton system which mirrors a skeleton filesystem onto the individual machines, depending on which class they're in. This is part of cfengine-masterconf (http://arpmats.sourceforge.net/ and go to cfengine-masterconf).

The background of this is that our college-level work with cfengine has caught the attention of campus IT as a possibly solution to manage our Mac's which currently aren't managed. The campus uses Novell Zenworks for windows management. One feature of Zenworks is that when a user logs in, applications that are associated with that user are immediately pushed out. We have a few roaming users who can benefit from this and Campus IT would be more amenable if I can prove that this is possible.

I would prefer that all application be local and installed everywhere, but some licenses forbid this and we just have too many applications and we don't have a network storage share in place for all of the Mac's.

I was thinking that in the system login script, we check the username against a list of usernames and associated applications. If a user is associated with an application, then the correct semi-permanent flag file would be touched. Cfengine would then install the application based on the existence of the flag file and tidy the semi-permanent flag files. We could even remove the application if the flag files doesn't exist. This would handle our roaming users. The only catches I see are as follows:
1. how to inform/lock out the user while the application is being pushed out.

Maybe roll out a script to all machines that just says "please wait for installation", and when the user logs in, put in a softlink to it which has the name of the executeable that they want.

2. how to do it immediately upon login.

        sudo cfagent -q

        :)

--
Kind Regards,
 
Tim Nelson
Server Administrator
 
P: 03 9934 0888
F: 03 9934 0899
E: tim.nelson@webalive.biz
W: www.webalive.biz
 
WebAlive Technologies
Level 1, Innovation Building
Digital Harbour
1010 La Trobe Street
Docklands Melbourne VIC 3008

This email (including all attachments) is intended solely for the named 
addressee. It is confidential and may contain legally privileged information. If
you receive it in error, please let us know by reply email, delete it from your 
system and destroy any copies. This email is also subject to copyright. No
part of it should be reproduced, adapted or transmitted without the written 
consent of the copyright owner.

Emails may be interfered with, may contain computer viruses or other defects 
and may not be successfully replicated on other systems. We give no
warranties in relation to these matters. If you have any doubts about the 
authenticity of an email purportedly sent by us, please contact us immediately.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]