Hi,
I was looking around a little bit and couldn't find an example
I could use. The Apple bug report isn't visible except to
anyone outside of Apple except perhaps those who reported it. Do
you know where I could find a copy of that bug report? I'm thinking
if I can reproduce some kind of error, I might be able to submit a
separate bug report of my own. I might just try more experimenting
with some of the code from APUE2e. I already tried compiling some
of their examples and looping, but the available examples are a
little different so I'll have to edit those and try running them
again.
http://www.apuebook.com/
It's funny that I mentioned SQLite file locking in an earlier
email. It turns out that Apple themselves had been having a
problem with the fcntl$UNIX2003 in their own Aperture software,
and it has to do with their use of SQLite which, of course, is
a bit buggy on Mac OS X. It looks to me that they must have done
some kind of hack-around on Aperture instead of fixing the kernel
level locking.
http://discussions.apple.com/message.jspa?messageID=5978074
I haven't looked inside of SQLite myself. Maybe Apple submitted
something to those maintainers that works around the problem.
Thanks,
Richard Ryan
Steve Emmerson wrote:
Richard,
Let me know if I should do this after reading my earlier reply on what
I've already done.
--Steve
On 10/28/2010 02:54 PM, Richard Ryan wrote:
Hi again,
The problem you mentioned was kind of interesting---sorry
I keep coming upon things a little at a time. If you have
an Apple Developer's login, you can go the web page for
Mac OS X fcntl, go to the bottom and log in to make the
bug report. I tried logging in and it let me get in. I'm
assuming you probably have a login if you have a compiler.
If not, you can get your free account here:
http://developer.apple.com/devcenter/mac/index.action
If you report your bug, you may be doing a favor for more
than LDM users (however, that last article indicates
they can take an awfully long time in responding, it's still
worth a try). Go to the bottom of this page, click on the
Bug Reporter link at the bottom and log in with your
developer user name and password.
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man2/fcntl.2.html
It's an interesting problem, please let me know how they
respond.
Richard Ryan
On 10/28/10 1:08 PM, Justin Greenfield wrote:
We experimented with running LDM on OS X, both Leopard and Snow Leopard.
Installation is fairly straightforward, I think we had to tweak a couple of the
perl scripts, but nothing difficult. When working, it works like a champ.
But....
The killer is there's a bug in OS X that locks up the product queue on a call to fcntl. We tried various configurations, file systems, etc, to work around this bug, for months and months.
Sometimes it would hit the bug within a few hours of startup, sometimes it
would go for weeks before it locked up. But inevitably, it got hung up.
Sampling the process in this state always revealed the same thing: stuck in the
bowels of fcntl.
We encountered it on 10.5 and 10.6. We wrote all kinds of scripts to detect
the hung process and restart the daemon, and they worked most of the time, but
sometimes the only solution was to reboot the machine.
In the end, it just wasn't going to be reliable enough, which is a true shame, because there are a lot of things we'd love to do with OS X. We gave up and ported our stuff to run on linux.
It's possible that a subsequent OS X update has fixed the issue, but I wouldn't
bet on it.
Justin
On Oct 28, 2010, at 1:01 PM, Richard A. Ryan wrote:
Hi again,
The last thing I wrote only mentioned how dscl replaces the
/etc configurations. It turns out launchd/launchctl commands
and files also replace some of the functionality of what's in
/etc, and I'm guessing there are probably other things. The
/etc/services file's functionality has something to do with
launchd/launchctl rather than dscl.
Again, for the Mac mini, if you want to do server type things
on it you might want to get the Mac mini preloaded with
Mac OS X Server because the user/group/account/networking/server
related command line calls are a bit hard to figure out. The
O'Reilly book ``Mac OS X for Unix Geeks'' doesn't seem to cover
everything and they also don't have a version for Snow Leopard.
Richard Ryan
-------- Original Message --------
Subject: [ldm-users] LDM on Mac OS X
Date: Wed, 27 Oct 2010 14:00:43 -0500
From: Tyler Allison <tyler@xxxxxxxxxxxxxxxx>
To: ldm-users@xxxxxxxxxxxxxxxx
Anybody running or been successful in running LDM on Mac OS X?
I'm considering playing with a MacMini as a small SOHO device running LDM.
I don't want to drop $1000 on a paper weight :) So hopefully someone
else has been there/done that.
-Tyler
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
_______________________________________________
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
