<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Steven Eppler's Blog &#187; mac os x</title>
	<atom:link href="http://www.steveneppler.com/blog/category/apple/mac-os-x/feed" rel="self" type="application/rss+xml" />
	<link>http://www.steveneppler.com/blog</link>
	<description>My life, technology, and everything in between</description>
	<lastBuildDate>Fri, 09 Jul 2010 17:05:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Fixing Mac OS X 10.6&#8217;s ping command (aka, removing Request timeout for icmp_seq #)</title>
		<link>http://www.steveneppler.com/blog/2010/03/31/fixing-mac-os-x-10-6s-ping-command-aka-removing-request-timeout-for-icmp_seq</link>
		<comments>http://www.steveneppler.com/blog/2010/03/31/fixing-mac-os-x-10-6s-ping-command-aka-removing-request-timeout-for-icmp_seq#comments</comments>
		<pubDate>Wed, 31 Mar 2010 21:12:14 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/?p=79</guid>
		<description><![CDATA[If you are like me, and annoyed that OS X 10.6&#8217;s ping command displays the following text when it cannot reach a host:

Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2

Then you&#8217;ll be happy for the fix.  You can either download the source code to the ping command from Apple [...]]]></description>
			<content:encoded><![CDATA[<p>If you are like me, and annoyed that OS X 10.6&#8217;s ping command displays the following text when it cannot reach a host:<br />
<code><br />
Request timeout for icmp_seq 0<br />
Request timeout for icmp_seq 1<br />
Request timeout for icmp_seq 2<br />
</code><br />
Then you&#8217;ll be happy for the fix.  You can either download the <a href="http://opensource.apple.com/source/network_cmds/network_cmds-325.1/ping.tproj/ping.c">source code</a> to the ping command from Apple and edit it yourself, or you can <a href="http://epplersoft.com/ping-fixed.tar.gz">download</a> my pre-compiled copy.</p>
<p>If you choose to edit it yourself, you&#8217;ll want to comment out lines 977 and 978 so they look like this:<br />
<code><br />
 // if (!(options &#038; F_QUIET))<br />
                                        // printf("Request timeout for icmp_seq %ld\n", ntransmitted - 2);<br />
</code></p>
<p>Then just type &#8216;gcc ping.c&#8217; and you&#8217;ll end up with a file called a.out, which you can use to replace /sbin/ping, or put in your local ~/bin directory if you&#8217;ve got one.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2010/03/31/fixing-mac-os-x-10-6s-ping-command-aka-removing-request-timeout-for-icmp_seq/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adding Printers to OS X from the Command Line</title>
		<link>http://www.steveneppler.com/blog/2009/07/09/adding-printers-to-os-x-from-the-command-line</link>
		<comments>http://www.steveneppler.com/blog/2009/07/09/adding-printers-to-os-x-from-the-command-line#comments</comments>
		<pubDate>Thu, 09 Jul 2009 20:04:12 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/?p=72</guid>
		<description><![CDATA[After a little searching, I found out you can add printers to OS X from the command line using this syntax:

lpadmin -p Printer_Name -L "Printer Location" -E -v lpd://x.x.x.x -P /Library/Printers/PPDs/Contents/Resources/en.lproj/Printer_Driver.gz

If you don&#8217;t specify the -P option, it will not show up in your Print or Printer Setup dialogs.  If you want to include [...]]]></description>
			<content:encoded><![CDATA[<p>After a little searching, I found out you can add printers to OS X from the command line using this syntax:<br />
<code><br />
lpadmin -p Printer_Name -L "Printer Location" -E -v lpd://x.x.x.x -P /Library/Printers/PPDs/Contents/Resources/en.lproj/Printer_Driver.gz<br />
</code></p>
<p>If you don&#8217;t specify the -P option, it will not show up in your Print or Printer Setup dialogs.  If you want to include the generic PPD, it is located here:</p>
<p><code>/System/Library/Frameworks/ApplicationServices.framework/Versions \ /A/Frameworks/PrintCore.framework/Versions/A/Resources/Generic.ppd</code></p>
<p>That path is all one line, with no spaces.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2009/07/09/adding-printers-to-os-x-from-the-command-line/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Leopard&#8217;s SSH Agent not working</title>
		<link>http://www.steveneppler.com/blog/2007/12/10/leopards-ssh-agent-not-working</link>
		<comments>http://www.steveneppler.com/blog/2007/12/10/leopards-ssh-agent-not-working#comments</comments>
		<pubDate>Mon, 10 Dec 2007 23:44:56 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[mac os x]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2007/12/10/leopards-ssh-agent-not-working</guid>
		<description><![CDATA[My Leopard SSH agent was not working after upgrading a Macbook Pro.  I was using a few other applications in the past to manage my SSH keys &#8211; in fact, I didn&#8217;t even know this was a feature until the new install on a Mac Pro worked without me installing the &#8216;keychain&#8217; app from [...]]]></description>
			<content:encoded><![CDATA[<p>My Leopard SSH agent was not working after upgrading a Macbook Pro.  I was using a few other applications in the past to manage my SSH keys &#8211; in fact, I didn&#8217;t even know this was a feature until the new install on a Mac Pro worked without me installing the &#8216;keychain&#8217; app from fink, or a number of other solutions that I had tried in the past.</p>
<p>To fix this, I had to edit the ~/.MacOSX/environment.plist file.  In that file, there is an entry for SSH_AUTH_SOCK which needs to be removed.  I just removed the the section that looked like:</p>
<pre>
&lt;key&gt;SSH_AUTH_SOCK&lt;/key&gt;
&lt;string&gt;/tmp/503/SSHKeychain.sock&lt;/string&gt;
</pre>
<p>The text may differ slightly on your computer.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2007/12/10/leopards-ssh-agent-not-working/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Leopard Error -5002 when connecting to AFP shares</title>
		<link>http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares</link>
		<comments>http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares#comments</comments>
		<pubDate>Fri, 26 Oct 2007 20:40:02 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares</guid>
		<description><![CDATA[When connecting to AFP shares in the new Mac OS X 10.5 (Leopard), you may get a -5002 error when the server only supports clear text passwords.  To resolve, either disable clear text passwords on the server side, or change the following plist:
~/Library/Preferences/com.apple.AppleShareClient.plist
You need to change the afp_cleartext_allow value to &#8220;Yes&#8221; &#8220;true&#8221; or &#8220;1&#8243; [...]]]></description>
			<content:encoded><![CDATA[<p>When connecting to AFP shares in the new Mac OS X 10.5 (Leopard), you may get a -5002 error when the server only supports clear text passwords.  To resolve, either disable clear text passwords on the server side, or change the following plist:</p>
<p>~/Library/Preferences/com.apple.AppleShareClient.plist</p>
<p>You need to change the afp_cleartext_allow value to <del datetime="2008-10-10T13:40:53+00:00">&#8220;Yes&#8221;</del> &#8220;true&#8221; or &#8220;1&#8243; (depending on the current values you see, either &#8220;false&#8221; or a &#8220;0&#8243;).</p>
<p>Here&#8217;s an excerpt from my file:</p>
<p><code><br />
...<br />
&lt;key&gt;afp_cleartext_allow&lt;/key&gt;<br />
&lt;true /&gt;<br />
&lt;key&gt;afp_cleartext_warn&lt;/key&gt;<br />
&lt;integer&gt;0&lt;/integer&gt;<br />
&lt;key&gt;afp_default_name&lt;/key&gt;<br />
&lt;string&gt;&lt;/string&gt;<br />
...<br />
</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2007/10/26/leopard-error-5002-when-connecting-to-afp-shares/feed</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Online Remote Backup with Mozy</title>
		<link>http://www.steveneppler.com/blog/2007/04/27/online-remote-backup-with-mozy</link>
		<comments>http://www.steveneppler.com/blog/2007/04/27/online-remote-backup-with-mozy#comments</comments>
		<pubDate>Fri, 27 Apr 2007 19:36:12 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[mac os x]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2007/04/27/online-remote-backup-with-mozy</guid>
		<description><![CDATA[Mozy is an online backup service &#8211; right now I&#8217;m using it to backup roughly 1.6GB of data.  You can backup 2GB for free, or pay around $5 per month for unlimited backup, which I am thinking about upgrading to.  Recently they released a Mac client which makes this a better option for me.  [...]]]></description>
			<content:encoded><![CDATA[<p><a target="_blank" href="http://www.mozy.com">Mozy</a> is an online backup service &#8211; right now I&#8217;m using it to backup roughly 1.6GB of data.  You can backup 2GB for free, or pay around $5 per month for unlimited backup, which I am thinking about upgrading to.  Recently they released a Mac client which makes this a better option for me.  They also offer a commercial version of the service which called <a target="_blank" href="http://www.mozypro.com">MozyPro</a>.</p>
<p><a href="http://www.downloadsquad.com/2007/04/26/backup-your-mac-online-with-mozy/">read more</a> | <a href="http://digg.com/apple/Backup_your_Mac_online_with_Mozy">digg story</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2007/04/27/online-remote-backup-with-mozy/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>InDesign Crashes Whilte Printing on Mac OS X</title>
		<link>http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x</link>
		<comments>http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x#comments</comments>
		<pubDate>Mon, 17 Apr 2006 17:11:43 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x</guid>
		<description><![CDATA[Sometimes, Adobe InDesign will crash when trying to print on a user account with a networked home folder under Mac OS X.  Here is the fix that I use:

ditto -rsrc /System/Library/Printers /Library/Printers

I send that command to all computers with the problem via ARD (Apple Remote Desktop) and it seems to resolve all of the [...]]]></description>
			<content:encoded><![CDATA[<p>Sometimes, Adobe InDesign will crash when trying to print on a user account with a networked home folder under Mac OS X.  Here is the fix that I use:</p>
<pre>
ditto -rsrc /System/Library/Printers /Library/Printers
</pre>
<p>I send that command to all computers with the problem via ARD (<a href="http://www.apple.com/remotedesktop/" target="_blank">Apple Remote Desktop</a>) and it seems to resolve all of the issues.</p>
<p>If that doesn&#8217;t work, you need to copy or create a Printers folder in the current users Library folder.  Drop into Terminal and type the following:</p>
<pre>
mkdir ~/Library/Printers
</pre>
<p>Those two methods have resolved most of our InDesign printing issues.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2006/04/17/indesign-crashes-whilte-printing-on-mac-os-x/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Locally Cache Mac OS X Network Login Folders</title>
		<link>http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders</link>
		<comments>http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders#comments</comments>
		<pubDate>Tue, 04 Apr 2006 15:21:22 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[mac os x]]></category>
		<category><![CDATA[on the job]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders</guid>
		<description><![CDATA[Here at the school district I was running into a problem where if several Mac OS X wireless clients logged into the network at once, everything slowed down to a crawl.  After researching the problem, it looked like the user&#8217;s Library and Microsoft User Data folders were causing the problem.  I tried turning [...]]]></description>
			<content:encoded><![CDATA[<p>Here at the school district I was running into a problem where if several Mac OS X wireless clients logged into the network at once, everything slowed down to a crawl.  After researching the problem, it looked like the user&#8217;s Library and Microsoft User Data folders were causing the problem.  I tried turning on OS X&#8217;s home folder syncronization, but that didn&#8217;t work very well, and filled up our older computers fast.  The solution I found was to locally cache the user&#8217;s Library and Microsoft User Data folder.  To do this, create a symbolic link from the user&#8217;s networked &#8216;Library&#8217; folder and point it to a local source.  I chose /tmp/UserCache/username/Library.  Here is the login script I created to automate the process:</p>
<pre>
#! /bin/bash

# Create local user caches of important directories
# Written by Steven Eppler 04/04/2006

export PATH=/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin

# Set user variable
user="$1"

# This grabs the user's home directory server
input=`dscl localhost read Search/Users/$user NFSHomeDirectory`
nethomedir=${input:18}

# Or you can hardcode it...
# nethomedir="/Network/Servers/ServerName/Volume/$user"

# Check for blank nethomedir - otherwise you will delete
# the root /Library folder!
if [ """$nethomedir""" != "" ]; then

echo $user
echo $nethomedir

# Create local caching directories
mkdir /tmp/UserCache
mkdir /tmp/UserCache/$user
mkdir /tmp/UserCache/$user/Microsoft\ User\ Data
mkdir /tmp/UserCache/$user/Library

# Give everyone rights to them...
chmod -R ugo=rwx /tmp/UserCache

# Create Documents and Desktop folder (sometimes they don't exist)
mkdir $nethomedir/Documents
mkdir $nethomedir/Desktop

# Delete old folders or links
rm -rf $nethomedir/Library
rm -rf $nethomedir/Documents/Microsoft\ User\ Data

# Create new links
ln -s /tmp/UserCache/$user/Library $nethomedir/Library
ln -s /tmp/UserCache/$user/Microsoft\ User\ Data $nethomedir/Documents/Microsoft\ User\ Data

fi
</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2006/04/04/locally-cache-mac-os-x-network-login-folders/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>First R/C Plane Video</title>
		<link>http://www.steveneppler.com/blog/2006/02/07/first-rc-plane-video</link>
		<comments>http://www.steveneppler.com/blog/2006/02/07/first-rc-plane-video#comments</comments>
		<pubDate>Tue, 07 Feb 2006 23:24:11 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[mac os x]]></category>
		<category><![CDATA[r/c]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2006/02/07/first-rc-plane-video</guid>
		<description><![CDATA[Here is a video of my first R/C flights.  On my first landing I almost hit the cameraman, but all was good &#8211; only bent the landing gear a tiny bit which was easily bent back.  The video turned out pretty good, and all was created/rendered using iLife &#8216;06 on Mac OS X [...]]]></description>
			<content:encoded><![CDATA[<p>Here is a video of my first R/C flights.  On my first landing I almost hit the cameraman, but all was good &#8211; only bent the landing gear a tiny bit which was easily bent back.  The video turned out pretty good, and all was created/rendered using iLife &#8216;06 on Mac OS X 10.4.3 (running on an AMD CPU&#8230;hmm&#8230;)</p>
<p>You can view the video <a href="http://www.youtube.com/?v=vby95CUXtqo" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2006/02/07/first-rc-plane-video/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Solution to the iTunes -208 Error Problem</title>
		<link>http://www.steveneppler.com/blog/2005/10/18/solution-to-the-itunes-208-error-problem</link>
		<comments>http://www.steveneppler.com/blog/2005/10/18/solution-to-the-itunes-208-error-problem#comments</comments>
		<pubDate>Tue, 18 Oct 2005 16:43:51 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[apple]]></category>
		<category><![CDATA[mac os x]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2005/10/18/19</guid>
		<description><![CDATA[If iTunes 6 is getting the -208 error, this article at Apple may help you get it fixed.
Remember when typing commands in Terminal &#8211; everything is pretty much cAsE sEnSiTiVe.
Apple &#8211; Discussions &#8211;  Solution to the iTunes -208 Error Problem
This link is now broken (apparently the discussion thread got closed).
Now you can just download [...]]]></description>
			<content:encoded><![CDATA[<p>If iTunes 6 is getting the -208 error, this article at Apple may help you get it fixed.</p>
<p>Remember when typing commands in Terminal &#8211; everything is pretty much cAsE sEnSiTiVe.</p>
<p><a href="http://discussions.info.apple.com/.68bc3e4c/0">Apple &#8211; Discussions &#8211;  Solution to the iTunes -208 Error Problem</a></p>
<p>This link is now broken (apparently the discussion thread got closed).</p>
<p>Now you can just download the iTunes 6 installer from Apple’s site. iTunes 6.0.1 fixed this issue.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2005/10/18/solution-to-the-itunes-208-error-problem/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>How I got my digg.com back&#8230;</title>
		<link>http://www.steveneppler.com/blog/2005/10/11/how-i-got-diggcom-back</link>
		<comments>http://www.steveneppler.com/blog/2005/10/11/how-i-got-diggcom-back#comments</comments>
		<pubDate>Tue, 11 Oct 2005 14:35:15 +0000</pubDate>
		<dc:creator>eppler</dc:creator>
				<category><![CDATA[linux]]></category>
		<category><![CDATA[mac os x]]></category>

		<guid isPermaLink="false">http://www.steveneppler.com/blog/2005/10/11/14</guid>
		<description><![CDATA[For a few weeks now, I have been unable to access digg.com through my work&#8217;s internet connection.  I have been unable to determine where the problem lies, so I decided to access it via an SSH tunnel.  Here is the command I used:
sudo ssh -l *_username_* -L:*_localport_*:*_remotehost_*:*_remoteport_* *_tunnelhost_*
With all the blanks filled in, [...]]]></description>
			<content:encoded><![CDATA[<p>For a few weeks now, I have been unable to access <a href="http://digg.com">digg.com</a> through my work&#8217;s internet connection.  I have been unable to determine where the problem lies, so I decided to access it via an SSH tunnel.  Here is the command I used:</p>
<p>sudo ssh -l *_username_* -L:*_localport_*:*_remotehost_*:*_remoteport_* *_tunnelhost_*</p>
<p>With all the blanks filled in, here is my final command:<br />
<code><br />
sudo ssh -l seppler -L:80:digg.com:80 epplersoft.com<br />
</code><br />
Then, I modifyed my /etc/hosts file to and added the following line:<br />
<code><br />
127.0.0.1       digg.com<br />
</code><br />
Now, I can access digg.com from work and home via my SSH tunnel.</p>
<p>&#8230;And that&#8217;s how I got my <a href="http://digg.com">digg</a> back.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.steveneppler.com/blog/2005/10/11/how-i-got-diggcom-back/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
