Tag Info

New answers tagged

4

You actually can set a password for the guest account. Use sudo passwd guest from the terminal.


0

Solution found here, I will file a big for that. https://discussions.apple.com/thread/4225458?tstart=0


0

Yes this is possible. When prompted for the location of the home folder for the user you can choose any shared folder that you have configured to be used as storage for home folders in the File Sharing service. This folder can be anywhere on the machine or anywhere on the network.


2

Ask your IT folks if they'd be OK with you running an OS X VM inside VMware Fusion and have admin rights inside the VM. That approach would allow you to get what you want (a developer environment where you could install things) while sandboxing it (which may satisfy the security rules and policies that your IT folks need to abide by.)


1

Make sure that all the permissions are correct on your home folder. You can use the ACL tool on the Recovery HD to do this: Boot into the Recovery HD using ⌘R. Run resetpassword in Terminal (available from Utilities → Terminal). Select your account from the drop-down list. Click the Reset button for Reset Home Directory Permissions and ACLs.


0

Go to Macintosh HD< Users< you should find your account name here < desktop< right click get info< give your self permission then apply this permission to all encloused items>


1

Just kill the loginwindow process. sudo pkill loginwindow You could get fancy and specify the user if multiple users have a loginwindow process, but this is an easy one shot, no prompt way to end a user's graphical session.


5

This has worked for me in the past: Log out (with confirmation) osascript -e 'tell app "System Events" to log out' Log out directly (no confirmation) osascript -e 'tell app "System Events" to «event aevtrlgo»' or osascript -e 'tell application "loginwindow" to «event aevtrlgo»' This way any running application will get noticed and can terminate ...


4

name (2) is your computer's hostname. You can change it in the 'Sharing' section of System Preferences:


1

You can not trivially launch graphical applications as another user. A Proxy Process is Required To launch a graphical application as another user, that user must be logged in to a graphical session and have a process running within their session able to launch your desired application. Prior to OS X 10.9, this could be approximated via the launchctl ...


0

If you were were to open AppleScript, you would use the following format: do shell script "/usr/bin/su - " & user & " -c " & "'" & cmd & "'" with administrator privileges password "blahblah" If you wanted to make a shell script, you'd need to chmod a+x the file and write it out like this: #!/usr/bin/env bash su -c ...


0

You can simply save your example as a text file adding the suffix .command or .sh to it to execute it with a double-click. AppleScript can call an .sh-script, too, with do shell script "/path/to/yourscript.sh" Not sure if Automator can do the same. But su basically only works with commands not using the Aqua GUI of Mac OS X. So if you try to open an ...


1

There is no way to do that. As soon as a user is switched, the inactive one looses all access to input/output devices on system-level.


1

Yes in Macosx ngroups is 16 Run "sysctl kern.ngroups" And btw it cannot be changed with "sysctl -w "


1

From the source code of newgrp if (ngrps == NGROUPS_MAX) warnx("too many groups"); and I think NGROUPS_MAX is defined as 16. That is given in syslimits.h


1

The groups command is not showing the correct ordering of groups in your user context. It is sorting group ids by gid. Use "id" the show your group set actually used by NFS. See "man groups" for details. Use the command "newgrp group" to change a group into the first place of the gid list.


0

The easiest way would be to create new user with admin privileges and delete all others. That should get rid off the unwanted. You can try rebuilding your user account as described here.


1

An erroneous extended attribute has been applied to this directory somehow, but it can only be removed using the xattr Terminal command. You should take a look at a brief explanation here. A more detailed question and answer can be found at this StackOverflow page.



Top 50 recent answers are included