Locking Down Finder Command Preferences Post: 302450743

Sponsored Content

Operating Systems OS X (Apple) Locking Down Finder Command Preferences Post 302450743 by [MA]Flying_Meat on Friday 3rd of September 2010 04:14:32 PM

09-03-2010

Registered User

Quote:

Originally Posted by unimachead

...but the complexity lies in deploying it under Aquaconnect's ability to allow deployment of the settings per user that authenticates within their terminal session.

Presumably, Aquaconnect spawns multiple user sessions via some display functionality, but the actual user session on the server is still identical to a single user logon at the physical server. no?

That is, a new user logging on to the server via Aquaconnect, still automagically gets a "default" home folder on that server, created in /Users/

If that is the case, then any admin user can modify the /System/Library/User\ Template/<language>.proj/Library/Preferences/ directory. That takes care of any new user accounts that are created on the server for remote sessions.
Then you can copy the MCX file to existing user's home folders on the server and change privs for that preference file as needed via a script 'er something?

As I recall, Aquaconnect was positioned as the Mac equivalent to RDC on the PC. If that is the case, then user sessions are spawned on the server

[MA]Flying_Meat

View Public Profile for [MA]Flying_Meat

Find all posts by [MA]Flying_Meat

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Bash shell: Creating Preferences

In OS X I'm currently writing a bash script that requires writing to preference file. I may eventually want to share it with users on other Unix-like OSs and would like to accommodate for that possibility ahead of time. Most OS X applications save preferences in xml-format plist files. These...

2. UNIX and Linux Applications

Bluefish: where are the preferences saved?

I have just tried out Bluefish as an alternative to my regular text editor. If I save the modified preferences and reboot, the preferences have to be reentered again. Does anyone know which file the preferences are saved in? The command find / -mmin -5 | grep bluefish yields zero hits. Thanks...

3. Ubuntu

Scripting sound preferences?

I'm finding myself changing sound preferences (specifically, output) frequently, and I'd like to write a shell script to do this for me. Does anyone know what command(s) to use?

4. Programming

Table Locking in Insert Command.

Hi, i have a java based tool which does insert operation in a TABLE, and in parallel the same table is used by my C++ code which does select Query. the Table will be always busy, but sometimes the table is getting locked when i try to make an insert, am bit confused whether the lock is...

5. UNIX for Advanced & Expert Users

Insert Command Creating Table Locking Problem

LEARN ABOUT DEBIAN

startx

STARTX(1)						      General Commands Manual							 STARTX(1)

NAME

       startx - initialize an X session

SYNOPSIS

       startx [ [ client ] options ... ] [ -- [ server ] [ display ] options ... ]

DESCRIPTION

       The  startx  script  is	a front end to xinit(1) that provides a somewhat nicer user interface for running a single session of the X Window
       System.	It is often run with no arguments.

       Arguments immediately following the startx command are used to start a client in the same manner as xinit(1).  The  special  argument  '--'
       marks  the  end	of  client  arguments  and the beginning of server options.  It may be convenient to specify server options with startx to
       change on a per-session basis the default color depth, the server's notion of the number of dots-per-inch the display device  presents,	or
       take  advantage	of  a  different  server layout, as permitted by the Xorg(1) server and specified in the xorg.conf(5) configuration.  Some
       examples of specifying server arguments follow; consult the manual page for your X server to determine which arguments are legal.

	      startx -- -depth 16

	      startx -- -dpi 100

	      startx -- -layout Multihead

       To determine the client to run, startx first looks for a file called .xinitrc in the user's home directory.  If that is not found, it  uses
       the  file  xinitrc in the xinit library directory.  If command line client options are given, they override this behavior and revert to the
       xinit(1) behavior.  To determine the server to run, startx first looks for a file called .xserverrc in the user's home directory.  If  that
       is  not	found,	it  uses  the file xserverrc in the xinit library directory.  If command line server options are given, they override this
       behavior and revert to the xinit(1) behavior.  Users rarely need to provide a .xserverrc file.  See  the  xinit(1)  manual  page  for  more
       details on the arguments.

       The system-wide xinitrc and xserverrc files are found in the /etc/X11/xinit directory.

ENVIRONMENT VARIABLES

       DISPLAY			This  variable	gets set to the name of the display to which clients should connect.  Note that this gets set, not
				read.

       XAUTHORITY		This variable, if not already defined, gets set to $(HOME)/.Xauthority.  This is to prevent the X server,  if  not
				given  the  -auth  argument,  from automatically setting up insecure host-based authentication for the local host.
				See the Xserver(1) and Xsecurity(7) manual pages for more information on X client/server authentication.

FILES

       $(HOME)/.xinitrc 	Client to run.	Typically a shell script which runs many programs in the background.

       $(HOME)/.xserverrc	Server to run.	The default is X.

       /etc/X11/xinit/xinitrc	Client to run if the user has no .xinitrc file.

       /etc/X11/xinit/xserverrc Server to run if the user has no .xserverrc file.

SEE ALSO

       xinit(1), X(7), Xserver(1), Xorg(1), xorg.conf(5)

X Version 11							    xinit 1.3.2 							 STARTX(1)