FontExplorer X Logout script

I'm rolling out FontExplorer X to our students and need a bit of help with the scripts to move the Fontdatabase file around.
My login script works as exspected but the logout script doesn't run at logout. It runs fine when a user is logged in
The script is attached as a LogoutHook.
Can someone help please??
!/bin/sh
username=`whoami`
userid=`/usr/bin/id -u`
userfolder=${username}_${userid}
userhome=`/usr/bin/id -P | cut -f9 -d:`
mv "/Users/Shared/Linotype/FontExplorer X/$userfolder/FontDatabase.db" "$userhome/Library/Font Temp/"
Message was edited by: nvp

The terminal command to use would be the following:
osascript -e 'tell application \"System Events\" to log out'
The AppleScript line to use would be this:
tell application "System Events" to log out
These can be put into a login hook script (http://support.apple.com/kb/HT2420) or can be put into an AppleScript application (which can be created with the Automator utility), which then can be placed in the user's login items so it runs at login.
The problem here is overcoming Apple's warning about automatically resuming your workflow, which appears at every logout.

Similar Messages

Logout Script not working in 10.9.3 Mavericks

Sorry for the duplicate post, but this issue is with MacBook Pro not iMac.
Can anyone tell me why this logoutscript will not work using LogouHook in Mavericks. The exact same script worked with Lion and Mountain Lion.
#!/bin/csh
## CCS-Checkout Logout Script
if ( $USER == 'ccs-checkout' ) then
#first, unlock all files
/usr/bin/chflags -R nouchg /Users/ccs-checkout/*
/usr/bin/chflags -R nouchg /Users/ccs-checkout/.Trash/
/usr/bin/chflags -R nouchg /Users/ccs-checkout/.??*
#then, delete all of the files
/bin/rm -R /Users/ccs-checkout
#copy a "clean" version of the ccs-checkout users home directory
/usr/bin/ditto -rsrcFork /var/skel/ccs-checkout /Users/ccs-checkout
#ensure that the users directory exists and set the privs
/usr/sbin/chown -R ccs-checkout:wheel /Users/ccs-checkout
/bin/chmod -R 775 /Users/ccs-checkout/
#make sure trash is empty
/bin/rm -R /Users/ccs-checkout/.Trash/
#make sure trash dir exists and set privs for trash and dot files
/bin/mkdir /Users/ccs-checkout/.Trash
/usr/sbin/chown -R ccs-checkout /Users/ccs-checkout/.??*
/bin/chmod -R 700 /Users/ccs-checkout/.??*
endif
exit 0
The script will run in terminal when copied and pasted from #first, unlock all of the files to exit 0.
When I run defaults write com.apple.loginwindow LogoutHook /usr/local/bin/LogoutScript the date on the com.apple.loginwindow.plist file changes so it is being modified.
Apparently there is something in:
#!/bin/csh
## CCS-Checkout Logout Script
if ( $USER == 'ccs-checkout' ) then
That Mavericks does not like or won't execute.
To duplicate this issue on your MBP make a user named ccs-checkout with normal permissions and autologon. After the first logon of the ccs-checkout user log out and log on as root and copy the ccs-checkout users local profile to the /var/skel/ folder. Then make the above script into an executable .sh file named LogoutScript and place it in the /usr/local/bin/ folder and run the above LogoutHook.
Thanks for any help with this issue.

This is the part of code where script fails. In 9.2 I haven't any kind of problems.
                    think(0.1);
               forms
               .tree(100,
                    "//forms:tree[(@name='ZVE_PREGLED_ZAVAROVANJE_0')]")
                    .expandNode(
                    "X");
                    think(0.1);
               forms
               .tree(101,
                    "//forms:tree[(@name='ZVE_PREGLED_ZAVAROVANJE_0')]")
                    .selectNode(
                    "XY");
                    think(0.1);
               forms
               .tree(102,
                    "//forms:tree[(@name='ZVE_PREGLED_ZAVAROVANJE_0')]")
                    .activateNode(
                    "XYZ");
                    think(0.1);
               forms
               .textField(103,
                    "//forms:textField[(@name='INFO_BLOCK_IZBRANA_ZAVAROVANJA_0')]")
                    .setFocus();
                    think(0.1);
               }

Using logout scripts in Workgroup Manager

Hi,
We are having trouble with running out of HD space due to large numbers of users not emptying trashes regularly in our video editing and audio post production labs. I'd like to run a script that empties all users' trashes on logout. Rather than set up logout hooks on all the computers (we have quite a few) I wanted to push down the logout script via WGM. However, i'm running into trouble, the scripts won't run. The com.apple.mcxloginscripts.plist in /Library/Managed Preferences has the field 'trustComment' with the value 'skipping scripts because directory node "/LDAPv3/(our XServe)" trust level is less than "FullTrust"'. Is there a certificate that needs to be in the keychain of the client machine before login or logout scripts can be pushed down by WGM? If not what needs to be configured before this can be made to work?
Thanks
Message was edited by: SipaTechnical

I forgot to add, I followed the instruction in WGM changing the settings of ~root/Library/Preferences/com.apple.loginwindow.plist, however, I wasn't too sure about the key "MCXscriptTrust", I don't know what binding settings it wants me to match.

How I can execute a user logout script in mountain lion?

I've read that logouthook have been deprecated but I can't find how execute a logout script without this method.
Anyone may help me?
Regards
Alessandro

Hello baltwo,
I've read these article yesterday but the first one is about the LoginHook that Apple, in the second article, says that are deprecated.
The second article say to use launchd instead LoginHook and LogoutHook.
I've tried to do this but launchd works (I think...) only to launch a login script with the option RunAtLoad.
Nothing is specified with regard to the logout script.
PS.
Launchd with login script work only with restart but not with a shutdown and a power-on ... I'm investigating this behavior!!
I'm sorry for my poor english.

I need a logout script that will erase the standard user account data after logout.

I have a lab of 35 Macbook Pros and I am trying to make it where when the user logouts, it will erase the data after they logout.
I have found several articles about deleting user accounts when they login through AD, but this is not the case.
Any help would be much help!

Then when they are at those system they do not Login and if they do have to enter a password it is whatever it is for the Base user account that is setup. Right?
I'd look at the Mac KB system to see if you can restrict saving to the local HDD but yet allow saving to a thumb drive or not.
To do what you want the system would need to keep track of all files saved from time X to time Y, and those times would be every changing. Not sure you are going to get there from here.
Not sure what you mean by Lab machines. I've worked in and gone to school at a Graphic art school and they have hundreds of Lab Mac's that each student must log into with there own user account when in different classes and when saving any of there work it gets saved on the server so it can be retrieved by them when they log into another system someplace else throughout the school or when using their own computer and connected to the schools network.
I wish you the best of luck with this project.

Bash script to terminated upon logout,

Hi all,
I have created a bash script - which start recording a camera device for security purpose, but I need the script to finish when the security user is logging out.
Any idea on how to do that?

sweetthdevil wrote:
Hi again,
sorry it took some time but I haven't had the time to look yet,
Back to the topic, I added the "pkill mencoder" at the begining of the file but it doesn't seem to work (because when shutting down the pc, the avi file created is broken - the index)
Any suggestion?
Difficult to say like this. If you kill mencoder by hand (not with the logout script); does this work properly? Maybe you have to wait that men,coder actualy exit before continuing:
PID=$(grep mencoder)
kill $PID
wait $PID
(work only if there is a single mencoder process).
But how did you start mencoder? (o processes receive a HUP signal if the terminal from which it has been opened is closed).
Last edited by olive (2011-03-04 00:58:30)

Java script auto logout

hi all,
I'm using java-script to auto-logout after 15 minutes.
its logging out successfully. If it is minimized the action is not performing.
Only it is maximized or its live in the screen, then only its performing the task
I want the operation has to perform if the page is minimized also.
please help!!!! :(
Thanking You
Glass Fish

Hi ganesh,
Find below the code and try to help me.
Thanking You.
Glass Fish
<body onmousemove="reset_interval()" onclick="reset_interval()" onkeypress="reset_interval()" onscroll="reset_interval()" >
<script type="text/javascript">]
function set_interval()
//the interval 'timer' is set as soon as the page loads
var timer=setInterval("auto_logout()",900000);
// the figure '10000' above indicates how many milliseconds the timer be set to.
//Eg: to set it to 5 mins, calculate 5min= 5x60=300 sec = 300,000 millisec. So set it to 3000000
function reset_interval()
//resets the timer. The timer is reset on each of the below events:
// 1. mousemove 2. mouseclick 3. key press 4. scroliing
//first step: clear the existing timer
var timer;
clearInterval(timer);
//second step: implement the timer again
var timer=setInterval("auto_logout()",900000);
function auto_logout()
//this function will redirect the user to the logout script
//alert("You have been logged out and forwarded to Login Page");
window.location="login.jsp";
alert("You are IDLE For more than 15 minutes,So,You have been logged out and forwarded to Login Page");
//window.forward("/login.jsp");
</script>

No keyboard at login window after logout

Hello all,
I'm just starting state testing and have been presented with a problem. When a student logs out of a machine in order to log into the testing account the login window won't accept input from the keyboard.
Bacground and details:
We have labs of computers using workgroup manager and open directory for management. In a normal lab the machine will boot to a login window. This is so that the preferences will be refreshed before a student logs in. The student will login as a local user (student) and procede to do whatever for the day.
We have recently started state mandated testing. I have set up an OD account which is very locked down and keeps the student on track while testing. This requires someone to log the normal user out and login as the OD user. This is where the problem arises.
About 50% of the time the keyboard will no longer funtion after logout. No keys of any sort work. The mouse still works. Even keystrokes through ARD do nothing. A end user is then required to reboot the system in order to do ANYTHING. This is not ideal for elementary kids.
From my digging in log files and poking around i noticed that the loginwindow process was hanging or crashing. If i kill the process the login window blinks and then works just fine. I'm sure i could write a logout script that drops a process into the background to kill the loginwindow process after so many seconds, but thats messy. Has anyone seen this? Any thoughts or solution? Only happens on a logout, never on an initial bootup.
I have found that 95% of these issues occur on Mac Mini's. I can consistantly replicate the issue on a mini. If i clone the mini to a macbook, i no longer have the problem (using carbon copy cloner). So either the hardware is part of the issue or the clone fixed something in the process.
OSX 10.5.8
/var/log/windowserver.log (on logout)
May 02 16:27:30 [252] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller loginwindow
May 02 16:27:32 [252] CGXRestartSessionWorkspace: session workspace exited for session 256 ( on console )
May 02 16:27:32 [252] loginwindow connection closed; closing server.
May 02 16:27:33 [352] Server is starting up
May 02 16:27:36 [352] CGXMappedDisplayStart: Unit 0: no display alias property
May 02 16:27:36 [352] kCGErrorFailure: IOHIDSetCursorEnable returns -536870208
May 02 16:27:36 [352] kCGErrorFailure: Set a breakpoint at CGErrorBreakpoint() to catch errors as they are returned
May 02 16:27:36 [352] CGXPerformInitialDisplayConfiguration
May 02 16:27:36 [352] Display 0x41dc9d00: VirtualDisplay Unit 0; Vendor 0x756e6b6e Model 0x76697274 S/N 0; online enabled built-in (0,0)[1280 x 1024], base addr 0xb0021000
May 02 16:27:36 [352] AGCAttach: Couldn't find any matches
May 02 16:27:43 [352] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x2 not owned by caller SecurityAgent
May 02 16:27:45 [352] kCGErrorIllegalArgument: CGXOrderWindow: Operation on a window 0x2 not owned by caller SecurityAgent

>kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x2 not owned by caller SecurityAgent
In those cases there may be threads and/or processes trying to do things with windows that they don't own. In other words, some programmers may have goofed up a little bit someplace.
But might try the one Helpful marked post here...
https://discussions.apple.com/thread/987826?start=0&tstart=0

LoadTest and Fusion/ADF scripts

I've been creating scripts against Oracles Webcenter using the Fusion/ADF module - they playback fine in OpenScript - but when used in LoadTest I have seen some extraordinary server loads against smalll numbers of VU's
To make it easier to diagnose I have created simple login /logout scripts & looking through the server logs comparing the manual vs OpenScript vs LoadTest runs
The Manaul & OpenScript entries show login & logout but the Loadtest entries only show login - is the any way of checking if the VU's have actually logged out as part of their session ?
connection persistence is set to false in LoadTest

OLT by default executes multiple iterations during load test. If you have login/logout steps in run block, these iterations could be the reason for more sessions. Regarding sign out test, you can use text matching tests for each request to make sure that the response received is as expected. That way, if log out fails, it will show up in the report.
Raj

Zenity shutdown script with Consolekit

Somehow we are at the new stage hal deprecated and its changes is not easy for newbies to follows. also changing sudoers is a dirty and not safe trick So:
The need for zenity script with these feature:
@ Consolekit +dbus
@Logout
@shoutdown
@restart
@suspend { should we add resume to rc.conf daemons arry? if yes where? at the end?}
@my be cancel
is really being felt.
So if someone how is able to change the old zentiy openbox script comes forward and do the job; we are all appreciating.

Here's my logout script, it's an edited version of one of the Openbox logout scripts. It requires python2 and pygtk, so no zenity, but I thought it might be useful for someone nonetheless. Oh, the suspend/sleep needs pm-utils installed.
#!/usr/bin/env python2
import pygtk
pygtk.require('2.0')
import gtk
import os
class DoTheLogOut:
# Cancel/exit
def delete_event(self, widget, event, data=None):
gtk.main_quit()
return False
# Suspend
def suspend(self, widget):
os.system("pm-suspend")
# Hibernate
def hibernate(self, widget):
os.system("pm-hibernate")
# Reboot
def reboot(self, widget):
os.system("dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart")
# Shutdown
def shutdown(self, widget):
os.system("dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop")
def __init__(self):
# Create a new window
self.window = gtk.Window(gtk.WINDOW_TOPLEVEL)
self.window.set_title("Afsluiten? Kies een optie:")
self.window.set_resizable(False)
self.window.set_position(1)
self.window.connect("delete_event", self.delete_event)
self.window.set_border_width(20)
# Create a box to pack widgets into
self.box1 = gtk.HBox(False, 0)
self.window.add(self.box1)
# Create cancel button
self.button1 = gtk.Button("_Annuleren")
self.button1.set_border_width(10)
self.button1.connect("clicked", self.delete_event, "Changed me mind :)")
self.box1.pack_start(self.button1, True, True, 0)
self.button1.show()
# Create suspend button
self.button2 = gtk.Button("_Sluimerstand")
self.button2.set_border_width(10)
self.button2.connect("clicked", self.suspend)
self.button2.connect("clicked", self.delete_event, "Force removal :(")
self.box1.pack_start(self.button2, True, True, 0)
self.button2.show()
# Create hibernate button
self.button3 = gtk.Button("S_laapstand")
self.button3.set_border_width(10)
self.button3.connect("clicked", self.hibernate)
self.box1.pack_start(self.button3, True, True, 0)
self.button3.show()
# Create reboot button
self.button4 = gtk.Button("_Opnieuw opstarten")
self.button4.set_border_width(10)
self.button4.connect("clicked", self.reboot)
self.box1.pack_start(self.button4, True, True, 0)
self.button4.show()
# Create shutdown button
self.button5 = gtk.Button("A_fsluiten")
self.button5.set_border_width(10)
self.button5.connect("clicked", self.shutdown)
self.box1.pack_start(self.button5, True, True, 0)
self.button5.show()
self.box1.show()
self.window.show()
def main():
gtk.main()
if __name__ == "__main__":
gogogo = DoTheLogOut()
main()
Last edited by Unia (2011-08-20 11:01:46)

Script to force WiFi release - Guest account

Hi.
I am desperately trying to find a script solution to solve a network problem i am having.
We have 4 public computers at a school "public area" (for students). We have created a
guest account that works satisfactory except for one thing, the wifi stays logged on
even if the account is logged out.
Each student has to log on using a web service in order to gain access to Internet.
This works great but when the student logs out of the guest account and a new student
opens the same account the Internet is still available using the first users id.
Does any one have a soulution for this ?
/Martin

Apple allows you to write a logout hook.
See:
http://chris-mccafferty.blogspot.com/2010/12/mac-os-x-login-and-logout-scripts.h tml
also:
http://www.macos.utah.edu/documentation/programming_and_scripting/login_and_logo ut_scripts/mainColumnParagraphs/00/document/20030219-Scripts.pdf

Launchd at logout

launchd allows you to start an application, say open a text editor, just as user gets the desktop (after logging into console) using the RunAtLoad option. Now, even though https://developer.apple.com/library/mac/documentation/macosx/conceptual/bpsystem startup/chapters/CustomLogin.html says otherwise, the logout script still works in 10.9. But it does not seem to behave the same way. What I want to do is
User tells computer to log her out of the console
Application is loaded and waits on user input.
User does her thing with said application and closes it
Logout procedure is completed and we are back to the login screen.
How can I do step 2?

The normal approach for this kind of thing is to have an app running in the background which blocks logout. If you create an applescript like the following, save it as a stay-open application, and then run it, you'll get the basic effect:
on quit
display dialog "No logout till I say so..."
if button returned of the result is "ok" then
continue quit
end if
end quit
This will cancel logout unless you click the "ok" button. You will (of course) want something more complex, but this should get you started.

User interaction while running a logout hook

Hi:
I've completed my very first scripting project - copying files from a user's bootcamp partition to an external drive to act as a daily backup.
It's a simple copy command that's set to copy the user's windows directory and to ignore any errors (those nasty windows .dat files). Works perfectly when I logout, no trouble at all.
Because this will be implemented for users with basic techno skills, I'd like to introduce a little user interaction into the script. I wrote a whole script to that includes applescripting to pop up dialog boxes, let the user choose if he/she wants the back to proceed, tell them how long it will take, etc.
On it's own as an application, this works fine, however I can't get it to work as part of the logout script. I'm assuming since the finder has quit, dialog boxes from the Applescript won't display?
Is there a way to get around this so I can run the script as part of the logouthook and have display dialogs/user interaction? My goal is for this to all happen automatically at logout/shutdown/restart with the user only having to select one of these options and not have to run a separate application.
Thanks

Hello
What I usually do when I know a procedure will take long, I change the cursor style before I call the procedure with:
set_application_property(cursor_style, 'BUSY');
and after the call to the procedure, you set it back to default.
set_application_property(cursor_style, 'DEFAULT');
I don't really have an answer for your problem, but this is another way to do it.
So I Hope this help.
Karine

FontExplorer + Network Home Directories = font amnesia

I'm a humble (tho ambitious) graphic design instructor trying to get network home directories working in my 30-seat design lab. At the beginning of January I migrated all workstations to a freshly built 10.4.4 universal image and updated (actually re-installed) my server and took it to 10.4.4.
In my testing of network home directories everything is working perfectly accept our font manager. (Even Word is playing nice thanks to a tip I found here!)
We started with FontAgent (cause we own 30 licenses), but quickly found that to be not very well adapted to a network home environment. (I did get the official work-around shell scripts from Insider Software, and those looked to be an easily broken kluge that only solve half the problem.)
So again following Gerrit's tips from here, I tried the latest version of FontExplorer which is supposed to support network home directories-- and it runs! (Unlike FontAgent.)
...but it has an incurable case of amnesia. In other words, as users move around from machine to machine, session to session, and day to day it always forgets all their fonts-- even though the actual font files always remain accessible in the same place.
Upon investigation, I can see that FontExplorer is actually doing something very similar to the FontAgent shell scripts. That is, whenever FontExplorer is launched in a NHD environment it creates a new "FontDatabase.db" file in a directory on the local drive:
Users/Shared/Linotype/FontExplorer X/{UserShortName}_{UserNumericID}/
and creates a symbolic back to the file's customary location in the user's networked Library:
/Application Support/Linotype/FontExplorer X/
The amnesia part comes in because I haven't found a way to get FontExplorer to start with-- or keep-- an already configured "FontDatabase.db" file. It constantly seems to be resetting itself with each login.
Does anyone have wisodm or suggestions on how to make FontExplorer remember its fonts?
Does anyone have any tips for getting any font manger to be totally functional in a network home environment?
PowerBook G4 Mac OS X (10.4.4)

Excellent tips, and thank you - they're very helpful for all involved!
I see that you're using NFS (and its behavior makes sense), but this might make your life a little easier if you were to use AFP for home directories again:
1. If you have an automounted network Library (/Network/Library), that would be perfect for housing a "starter set" of Font Explorer preferences and your initial, preconfigured database file, in this way.
Create a folder in your automounted network Library and name it something like FEInitialData. Set the permissions such that your users can only read (root:admin 775 would be good). Now your clients all see the FEInitialData folder in /Network/Library/FEInitialData.
Locate these files from an appropriately configured local user account: com.linotype.FontExplorer.plist and the ~/Library/Application Support/Linotype/FontExplorer X folder (that contains the FontDatabase.db file).
Place a copy of the com.linotype.FontExplorer.plist file in the FEInitialData folder in your network Library. (To clients, this appears as /Network/Library/FEInitialData/com.linotype.FontExplorer.plist.)
Use Disk Utility to create a new disk image from the local ~/Library/Application Support/Linotype folder. Make sure that the image is a read/write image, and name it something like FESupport.dmg. Then place that resulting disk image in the network Library, so that to clients, this appears as /Network/Library/FEInitialData/FESupport.dmg.
2. Utilize an AppleScript app as a login item to perform the following listed actions at login time. You'll have to either distribute the login app to each computer (e.g. in their respective Applications folders), or place it in the automounted Library (or automounted Applications, etc.) like /Network/Library/LoginScript.app. You'll also have to define the script as a login item for your users. You can do that at the group level in Workgroup Manager once you have the LoginScript.app in the same relative place on each client.
Be sure also to remove FontExplorer X itself as a login item, since it needs to be quit while we're preparing files for it!
Listed Actions to be done by LoginScript.app:
1. If no ~/Library/Preferences/com.linotype.FontExplorer.plist file exists, copy it from /Network/Library/FEInitialData.
2. If no ~/FESupport.dmg file exists, copy it from /Network/Library/FEInitialData.
3. Mount the FESupport.dmg file to a local filesystem path, so that its contents appear to reside in a local folder. (For this script, I'll use /tmp.)
4. Ensure that a ~/Library/Application Support/Linotype folder exists and contains a symbolic link named "Font Explorer X" which points to the mounted disk image's contents.
5. Launch Font Explorer. (Upon initial launch, the metadata caches should be recreated.)
-----LoginScript.app---
(*See if the preference file and FESupport disk image are in the right places. If not, copy them there.*)
try
do shell script "ls ~/Library/Preferences | grep 'com.linotype'"
on error
--The com.linotype.FontExplorer.plist file is missing.
do shell script "cp /Network/Library/FEInitialData/com.linotype.FontExplorer.plist ~/Library/Preferences/com.linotype.FontExplorer.plist"
end try
try
do shell script "ls ~ | grep 'FESupport.dmg'"
on error
--The disk image is missing.
do shell script "cp /Network/Library/FEInitialData/FESupport.dmg ~/FESupport.dmg"
end try
(*Create the mount point for the FESupport.dmg file*)
try
--Delete the mount point in case we're not the first login and to ensure that we have an empty folder owned by this user.
do shell script "rm -rf /tmp/FEMountPoint"
end try
try
--Create the mount point
try
do shell script "mkdir /tmp/FEMountPoint"
end try
(*Ensure that we have a symbolic link to the mount point*)
try
--Remove any existing links just to be safe.
do shell script "rm -rf \"~/Library/Application Support/Linotype\""
end try
try
--Create new symbolic links.
do shell script "mkdir \"~/Library/Application Support/Linotype\""
do shell script "ln -s \"/tmp/FEMountPoint/FontExplorer X\" \"~/Library/Application Support/Linotype/FontExplorer X\""
(*Mount the ~/FESupport.dmg file to /tmp/FEMountPoint*)
do shell script "hdiutil attach ~/FESupport.dmg -mountpoint /tmp/FEMountPoint"
(*Open FontExplorer*)
do shell script "open \"/Applications/Linotype FontExplorer X.app\""
---End Script---
I might have messed up some of the syntax, so consider this a working example. Hope it helps!
And, yes, if you need consulting, you can find my contact info at consultants.apple.com/consultant by searching for AuburnMac.
--Gerrit

Logout Hook to kill Window Server

Hi there,
I have a problem with my users hanging at logout, the computer just freezes still displaying the desktop picture and doesn't make it to the login window.
I've tried to track down the cause to no avail. I can still ssh into the machine that's frozen and force a reboot remotely, kill the Window Server or do a hard reset.
None of these are ideal so I'd thought perhaps a logout script to kill the Window Server!?
Trouble is I don't seem to be having much luck trying to implement it. I can find lots of stuff about logout hooks in Tiger but not much in Leopard. I know you're supposed to be able to set them through Workgroup Manager but despite making my scripts executable, I can't get workgroup manager to see them as selectable when I try to add one.
I'm also confused about setting the appropriate login window preferences in ~root/Library/Preferences/com.apple.loginwindow.plist
Can anybody point me in the right direction?
Thanks in advance!

I looked through the report compiled and I found that APE (Application Enhancer) was still being called even though it doesn't exist along with OSS3D which wasn't working either. I got rid of both of those using their provided installers and it appears to work. WindowServer didn't crash which usually triggers the abnorminally high cpu usage.

FontExplorer X Logout script

Similar Messages

Maybe you are looking for