Need help with getting a login script to work with a login hook.

Question

Need help with getting a login script to work with a login hook.

I have tried three methods to implement a login script on OS X 10.6.8 Snow Leopard. I am trying to get the third method to work because, if I understand correctly, it runs in the background without anything appearing on the screen.

The first method involves an AppleScript saved as an application that is added to the list of login items via System Preferences in the Accounts pane. When the account is logged in, an AppleScript icon briefly appears and disappears on the Dock.

The second method involves a Terminal shell script that is saved with the name “login.command”, made executable via the Terminal command line, and then is added to the list of login items via System Preferences in the Accounts pane. Using this method, when the account is logged in, a Terminal window opens.

The third method involves a login hook. It does not seem to work, although a similarly configured logout hook does work. This method uses a Terminal shell script also. The shell script is saved with the name “loginscript” in the folder at the location “/usr/local/bin”, and the script is made executable via the Terminal command line. Then, the below commands are run on the Terminal command line:

sudo defaults write com.apple.loginwindow LoginHook /usr/local/bin/loginscript

sudo defaults read com.apple.loginwindow

Might anyone know how to make the third method work? I can provide more details of what I have done, if necessary.

Posted on Jul 13, 2013 4:44 AM

Reply

Answer 1

Jul 13, 2013 5:49 AM in response to John with a G4

It would be a good idea to post your "loginscript". In the mean time here's a link to the Daemon and Services Programming Guide- http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPSystem Startup/Chapters/CustomLogin.html

Reply

Answer 2

Jul 13, 2013 6:16 AM in response to Mark Jalbert

Regarding the code of the script, I tried two versions. Below is the first version:

#!/bin/bash

say "Hello, hello, hello. This is the startup script."

Below is the second version:

#!/bin/bash

#say "Hello, hello, hello. This is the startup script."

/usr/bin/osascript ~/Desktop/login_script.scpt

The AppleScript file “login_script.scpt” itself also has the "say" command in it.

Neither version produces any sound. Also, I double-checked the system volume to make sure that it was audible.

Reply

Answer 3

Jul 13, 2013 6:28 AM in response to John with a G4

First never assume that your shell and the operating system mechanism running a script have the same environment. So use absolute paths to commands and arguments. Post back the command and the text output from the following->

grep -w 'console' /private/etc/ttys

Reply

Answer 4

Jul 13, 2013 6:43 AM in response to Mark Jalbert

Below is the output from “grep -w 'console' /private/etc/ttys”:

#console "/usr/libexec/getty std.57600" vt100 on secure

console "/System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow" vt100 on secure onoption="/usr/libexec/getty std.9600"

Reply

Answer 5

Jul 13, 2013 8:36 AM in response to John with a G4

My best guess is the script is executed very early in the login process. Hence you do not hear any sound. Something as trivial as this doesn't belong in a loginhook.

Reply

Answer 6

Jul 13, 2013 9:02 AM in response to Mark Jalbert

Thank you for taking the time to help, and for sharing your insights.

Reply

Answer 7

BobHarris

Level 9

53,045 points

Jul 13, 2013 11:11 AM in response to John with a G4

NOTE: The loginhook environment is minimum

pwd:

/

	id -a:	uid=0(root)
	gid=0(wheel)
	egid=80(admin)
	groups=0(wheel),
	1(daemon),
	2(kmem),
	8(procview),
	29(certusers),
	3(sys),
	9(procmod),
	4(tty),
	5(operator),
	80(admin),
	20(staff)

$1:

psmith

	printenv: PWD=/
	SHLVL=1
	SECURITYSESSIONID=449a3aa0
	_=/usr/bin/printenv

Notice, no PATH, no USER environment variables, just about

nothing as an environment.

So, the 'say' command will not be found.

You can try

/usr/bin/say "Hello, hello, hello. This is the startup script."

and see how that works

Reply

Answer 8

Jul 13, 2013 11:30 AM in response to BobHarris

Thank you. I plan to give the full path a try.

Reply

Answer 9

Jul 13, 2013 2:55 PM in response to BobHarris

In the code of the shell script named “loginscript”, using the full path listed below solved the issue:

/usr/bin/say

Thank you for your help, Mr. Harris.

Reply