NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Yeah, I've filed plenty of bugs on OS X over the years, but I did not file one
for this. My bugs have been submitted and resolved and marked closed on the
time scale of 6-8 months, heck I still have one dated 4-20-2005 that's marked
"open". I just didn't have 6-8 more months to wait for a resolution.
Here's the last sample I can find on my system from an ldm lockup:
Analysis of sampling rpc.ldmd (pid 98748) every 1 millisecond
Call graph:
9039 Thread_2603
9039 start
9039 main
9039 read_conf
9039 invert_request_acl
9039 req6_new
9039 one_svc_run
9039 svc_getreqsock
9039 ldmprog_6
9039 hereis_6_svc
9039 down6_hereis
9039 dh_saveDataProduct
9039 pq_insert
9039 pq_insertNoSig
9039 ctl_get
9039 mm0_ftom
9039 rgn_lock
9039 fd_lock
9039 fcntl$UNIX2003
9039 fcntl$UNIX2003
I also believe this bug is called out in the LDM "known problems" docs as an
issue and notes that a bug has been filed with Apple as of 2008, which predates
our attempts.
I know from experience that the more people that report a bug, even if it gets
marked duplicate, the more likely the bug is to be addressed, so those of you
who are pursuing ldm on OS X should collect the proper data and file a bug at
http://bugreport.apple.com.
Justin
On Oct 28, 2010, at 3: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 archives: