<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Changing the default Template in Mac OS X</title>
	<link>http://yamahito.net/blog/2007/10/11/changing-the-default-template-in-mac-os-x/</link>
	<description>Tomos Hillman's mind-dump.</description>
	<pubDate>Thu, 11 Mar 2010 07:31:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: yamahito</title>
		<link>http://yamahito.net/blog/2007/10/11/changing-the-default-template-in-mac-os-x/#comment-1579</link>
		<pubDate>Sat, 20 Oct 2007 13:11:07 +0000</pubDate>
		<guid>http://yamahito.net/blog/2007/10/11/changing-the-default-template-in-mac-os-x/#comment-1579</guid>
					<description>Hi Ray,

As SB says, it sounds like the permissions issues is to do with this group folder - what are the permissions of the newly created file?  where's the folder located (network or local)?  What was the behaviour like before you created the default template?  You may find options in Workgroup Manager to change the default permissions of files created in the group folder, if WM is what is sharing it.

OS X should be resetting the permissions of the files in any template to the new user's when creating the account, which is why it seems unlikely that it's related to the template itself.  Otherwise the user wouldn't be able to access their own files, everything in the template being owned by root:wheel.

The method above is really for templates for local accounts which authenticate to the network, rather than whole accounts stored on OS X Server.  Having said that, it's an area I'm interested in myself, so I'd be interested in any information you have.  I'm guessing that, where locally the machine would create new accounts as they're needed, Server forces you to create the accounts ahead of time?  If so, that sounds like a bit of a pain.</description>
		<content:encoded><![CDATA[<p>Hi Ray,</p>
<p>As SB says, it sounds like the permissions issues is to do with this group folder - what are the permissions of the newly created file?  where&#8217;s the folder located (network or local)?  What was the behaviour like before you created the default template?  You may find options in Workgroup Manager to change the default permissions of files created in the group folder, if WM is what is sharing it.</p>
<p>OS X should be resetting the permissions of the files in any template to the new user&#8217;s when creating the account, which is why it seems unlikely that it&#8217;s related to the template itself.  Otherwise the user wouldn&#8217;t be able to access their own files, everything in the template being owned by root:wheel.</p>
<p>The method above is really for templates for local accounts which authenticate to the network, rather than whole accounts stored on OS X Server.  Having said that, it&#8217;s an area I&#8217;m interested in myself, so I&#8217;d be interested in any information you have.  I&#8217;m guessing that, where locally the machine would create new accounts as they&#8217;re needed, Server forces you to create the accounts ahead of time?  If so, that sounds like a bit of a pain.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: SilentBob</title>
		<link>http://yamahito.net/blog/2007/10/11/changing-the-default-template-in-mac-os-x/#comment-1578</link>
		<pubDate>Sat, 20 Oct 2007 12:47:51 +0000</pubDate>
		<guid>http://yamahito.net/blog/2007/10/11/changing-the-default-template-in-mac-os-x/#comment-1578</guid>
					<description>I haven't played around with user templates in OSX, but it sounds like you've got a permissions problem (that's unrelated to the template). You should be able to tell the permissions using the ls command (e.g. ls -l), which should tell you the owner and group associated with the file/folder. If you need to modify the permissions, privileged users can use chown, unprivileged users can use chgrp (if they're the owner of the file). If the file is already assigned to the correct group but other members can't access it, you (or the owner) may have to use chmod to change the permissions so that members of the group have access (whether you want to give them read or read-write access is up to you/the user). If you want subsequent files in the group folder to be given the group permission when files are placed in there, you may want to investigate using the setgid bit. If the setgid bit on a directory entry is set, files in that directory will have the group ownership as the directory, instead of than the group of the user that created the file. The setgid bit can be set using the chmod command. If you're not feeling too confident, it's probably worth reading the man pages for chmod, chown, chgrp, and reading up on file system permissions: http://en.wikipedia.org/wiki/File_system_permissions</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t played around with user templates in OSX, but it sounds like you&#8217;ve got a permissions problem (that&#8217;s unrelated to the template). You should be able to tell the permissions using the ls command (e.g. ls -l), which should tell you the owner and group associated with the file/folder. If you need to modify the permissions, privileged users can use chown, unprivileged users can use chgrp (if they&#8217;re the owner of the file). If the file is already assigned to the correct group but other members can&#8217;t access it, you (or the owner) may have to use chmod to change the permissions so that members of the group have access (whether you want to give them read or read-write access is up to you/the user). If you want subsequent files in the group folder to be given the group permission when files are placed in there, you may want to investigate using the setgid bit. If the setgid bit on a directory entry is set, files in that directory will have the group ownership as the directory, instead of than the group of the user that created the file. The setgid bit can be set using the chmod command. If you&#8217;re not feeling too confident, it&#8217;s probably worth reading the man pages for chmod, chown, chgrp, and reading up on file system permissions: <a href="http://en.wikipedia.org/wiki/File_system_permissions" rel="nofollow">http://en.wikipedia.org/wiki/File_system_permissions</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ray</title>
		<link>http://yamahito.net/blog/2007/10/11/changing-the-default-template-in-mac-os-x/#comment-1577</link>
		<pubDate>Sat, 20 Oct 2007 12:07:14 +0000</pubDate>
		<guid>http://yamahito.net/blog/2007/10/11/changing-the-default-template-in-mac-os-x/#comment-1577</guid>
					<description>Hi, i used this on an osx server for work group manager to create customized user home folders.  What im finding now is that when one user creates a file/folder and places it into a group folder, other members of the group can't open it.  Just to clarify, it is a permissions issue?  if so, after over 200-300 users already created, is there a way to change the permissions with too much pain!</description>
		<content:encoded><![CDATA[<p>Hi, i used this on an osx server for work group manager to create customized user home folders.  What im finding now is that when one user creates a file/folder and places it into a group folder, other members of the group can&#8217;t open it.  Just to clarify, it is a permissions issue?  if so, after over 200-300 users already created, is there a way to change the permissions with too much pain!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
