Sharing causes runaway smbd processes...

Discussion in 'Parallels Desktop for Mac' started by rft, May 30, 2006.

  1. rft

    rft

    Messages:
    31
    In Beta6 I have used MacOSX Windows Sharing and access via
    \\hostname\user in Parallels/XP. Now in the release candidate
    this does not work (I do not get access) and on the MacOS X side
    every second or so after the access attempt, a new smbd process
    is spawned, until the machine is unuseable, due to the limited size
    of the process table.

    Has anyone seen this problem? Or is there a stable way of accessing
    the OS X files? I have tried the Parallels Shared folder and this
    consistently crashes Explorer.

    Thanks in advance for any help,
    -- Robert
     
  2. bketelsen

    bketelsen Bit Poster

    Messages:
    9
    a dollar

    I bet a dollar this is the problem I had with the "-10810 can not launch <application>" errors I was seeing. I just enabled the shared folder yesterday to move a big ISO between environments. And I did a full reinstall of Mac OS X to solve the problem.
     
  3. rft

    rft

    Messages:
    31
    Possibly an unreachable printer server in /etc/cups/client.conf

    looking at /var/log/samba/log.smbd the CUPS printer server which I use at work could
    (obviously) not be reached when I was not at my workplace. This seems to trigger the
    runaway smbd processes, once the smbd process is triggered, which of course happens
    when I try to access MacOS X files from Parallels/XP.

    I removed the printer server from /etc/cups/client.config, and will try using the BrowsePoll
    feature as described in:
    http://math.berkeley.edu/index.php?module=faq&FAQ_op=view&FAQ_id=20

    After the change, the runaway smbd proccesses problem has not appeared yet. I shy away
    from switching it back just to confirm the bug, as this is a nasty problem...

    So this may be a bug in smbd.

    Greetings
    -- Robert
     
  4. rft

    rft

    Messages:
    31
    Cups printer server in /etc/cups/client.conf not at fault...

    I now had a runaway smbd problem without this setting.

    Greetings,
    -- Robert
     

Share This Page