What is "deny mach-per-user-lookup"

I went to console to investigate system crashes (i believe to be an openGL issue unrelated to this) and i saw a number of these:
5/26/10 1:22:42 AM sandboxd[330] sshd(1056) deny mach-per-user-lookup
There were 883 messages over 8.5 hours, mixed in with occasional:
Allow sshd-keygen-wrapper connecting from 217.27.150.178:55936 to port 22 proto=6
I traced the IP back to Kiev… in Russia. That's odd. I did a search around and found mention of people with snow leopard, 10.6.2 or 3 (which i have) reporting this but the conversations were varied…
could someone explain 'deny mach-per-user-lookup' for me, and elaborate on the sshd attempts? I don't know if i should be concerned. I do have an RSA key-only tunnel set up with my work computer, but i had believed this was to be the most secure set up possible and these seem to be on port 22 which is common FTP anyway. OS firewall is up otherwise allowing the common connections like fire sharing and SHH, my router is set for 'inbound and outbound accept' as its security policy, but regardless, all but a couple dozen specific ports are blocked.
Thanks for any input—

Nmap scan report for 217.27.150.178.sitel.com.ua (217.27.150.178)
Host is up (0.24s latency).
Not shown: 89 closed ports
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
25/tcp open smtp
80/tcp open http
110/tcp open pop3
135/tcp filtered msrpc
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
1720/tcp filtered H.323/Q.931
3128/tcp open squid-http
3306/tcp filtered mysql
From the scan, it appears to be some sort of server, possibly a private proxy server.
Perhaps someone is using it to anonymously attempt connecting to your machine.
Unless you are running a server, I say you need to beef up your security a bit. Close up
some of those ports you have opened up to the Internet.

Similar Messages

  • Com.apple.WebKit deny mach-per-user-lookup

    Hi all
    My console log is full of these:
    PM kernel: Sandbox: com.apple.WebKit (####) deny mach-per-user-lookup
    Anyone have any idea what this means and should something be done about it?
    Thanks

    As do I.  I can see that there is the usual overwhelming response to a problem.

  • What is the term " per user" in sqlserver developer edition licensing .

    Folks,
    I have to test my product with SQL Server 2012 database. Based on the search on ineternet, I know I have to get hold of Developer Edition
    and i should  go with  "per user" licensing model  for Developer edition . I am a bit confused here on what type of users they are ?
    SQL DB Administrator user
    Application Users account accessing the Database
    System Account accessing the Database
    Can some one please clarify.
    Thanks

    The Product Use Rights document is installed with the instance. EG
    C:\Program Files\Microsoft SQL Server\120\License Terms\SQLServer2014_License_DEV_1033.rtf
    Which states in relevant part
    1.   
    INSTALLATION AND USE RIGHTS.
    a.   
    General. One user may install and use copies of the software to design, develop, test and demonstrate your programs. You may not use the software on a
    device or server in a production environment.
    b.   
    Demonstration. Any person that has access to your internal network may install and use copies of the software to demonstrate use of your programs with
    the software. Those copies may not be used for any other purpose.
    c.    
    User Testing. Your end users may access the software to perform acceptance tests on your programs.
    David
    David http://blogs.msdn.com/b/dbrowne/

  • What's this sandboxd mdworker deny mach-lookup thing about?

    My newer iMac keeps locking up over many months. It seems to be getting more frequent. All updated are made and I'm running OS10.8.2.
    Each time I've looked at the console log one of the last entries has been related to mdworker and sandboxd.
    This is the console immediatly surrounding the latest lockup and restart (having to use the powerbutton.)
    3/10/13 7:48:27.128 PM com.apple.backupd[20992]: Backup completed successfully.
    3/10/13 7:48:27.000 PM kernel[0]: Sandbox: sandboxd(21005) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:50:27.573 PM mdworker[21015]: Unable to talk to lsboxd
    3/10/13 7:50:27.577 PM mdworker[21014]: Unable to talk to lsboxd
    3/10/13 7:50:27.622 PM sandboxd[21016]: ([21015]) mdworker(21015) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.626 PM sandboxd[21016]: ([21014]) mdworker(21014) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.000 PM kernel[0]: Sandbox: sandboxd(21016) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:52:28.404 PM mdworker[21026]: Unable to talk to lsboxd
    3/10/13 7:52:28.408 PM mdworker[21027]: Unable to talk to lsboxd
    3/10/13 7:52:28.457 PM sandboxd[21028]: ([21026]) mdworker(21026) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.461 PM sandboxd[21028]: ([21027]) mdworker(21027) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.000 PM kernel[0]: Sandbox: sandboxd(21028) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 10:04:58.000 PM bootlog[0]: BOOT_TIME 1362978298 0
    3/10/13 10:05:24.000 PM kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    3/10/13 10:05:24.000 PM kernel[0]: vm_page_bootstrap: 3994120 free pages and 167416 wired pages
    3/10/13 10:05:24.000 PM kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
    3/10/13 10:05:24.000 PM kernel[0]: zone leak detection enabled
    3/10/13 10:05:24.000 PM kernel[0]: standard timeslicing quantum is 10000 us
    3/10/13 10:05:24.000 PM kernel[0]: standard background quantum is 2500 us
    3/10/13 10:05:24.000 PM kernel[0]: mig_table_max_displ = 74
    3/10/13 10:05:24.000 PM kernel[0]: corecrypto kext started!
    3/10/13 10:05:24.000 PM kernel[0]: Running kernel space in FIPS MODE
    Below is the full report from the line in red above --
    mdworker(21027) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [21027]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x107e3e000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [285]
    Date/Time:       2013-03-10 19:52:28.457 -0700
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib                  0x00007fff8ca62686 mach_msg_trap + 10
    1   CoreFoundation                          0x00007fff93f47803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                          0x00007fff93f4cee6 __CFRunLoopRun + 1078
    3   CoreFoundation                          0x00007fff93f4c6b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                          0x00007fff93f5b371 CFRunLoopRun + 97
    5   mdworker                                0x0000000107e46ba9
    6   libdyld.dylib                           0x00007fff94edb7e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib                  0x00007fff8ca64d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff94d8c9ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff8ca626c2 semaphore_wait_trap + 10
    1   libxpc.dylib                            0x00007fff94f48e1f xpc_connection_send_message_with_reply_sync + 127
    2   LaunchServices                          0x00007fff8e8ec3ce send(LSBoxMessage&, LSBoxMessage&) + 28
    3   LaunchServices                          0x00007fff8e96cd4b lsbox_preflightAppLaunch + 84
    4   LaunchServices                          0x00007fff8e8f7341 _LSFindOrRegisterBundleNode + 857
    5   LaunchServices                          0x00007fff8e953b02 _LSRegisterNode + 75
    6   LaunchServices                          0x00007fff8e8ffa0f _LSBundleCopyOrCheckNode + 1047
    7   LaunchServices                          0x00007fff8e8e75b6 _LSCopyLibraryItemURLs + 486
    8   mdworker                                0x0000000107e6e014
    9   libdispatch.dylib                       0x00007fff94d8df01 _dispatch_call_block_and_release + 15
    10  libdispatch.dylib                       0x00007fff94d8a0b6 _dispatch_client_callout + 8
    11  libdispatch.dylib                       0x00007fff94d8b47f _dispatch_queue_drain + 235
    12  libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    13  libdispatch.dylib                       0x00007fff94d8b1c3 _dispatch_worker_thread2 + 249
    14  libsystem_c.dylib                       0x00007fff89e9ccab _pthread_wqthread + 404
    15  libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff8ca646d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff89e9ccb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff8ca646d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff89e9ccb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib                  0x00007fff8ca62686 mach_msg_trap + 10
    1   liblaunch.dylib                         0x00007fff918217c4
    2   liblaunch.dylib                         0x00007fff918204d9 bootstrap_look_up3 + 69
    3   libxpc.dylib                            0x00007fff94f46c21 _xpc_connection_bootstrap_look_up_slow + 371
    4   libxpc.dylib                            0x00007fff94f45c82 _xpc_connection_init + 1062
    5   libdispatch.dylib                       0x00007fff94d8a0b6 _dispatch_client_callout + 8
    6   libdispatch.dylib                       0x00007fff94d8b47f _dispatch_queue_drain + 235
    7   libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    8   libdispatch.dylib                       0x00007fff94d8b448 _dispatch_queue_drain + 180
    9   libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    10  libdispatch.dylib                       0x00007fff94d8b1c3 _dispatch_worker_thread2 + 249
    11  libsystem_c.dylib                       0x00007fff89e9ccab _pthread_wqthread + 404
    12  libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Binary Images:
           0x107e3e000 -        0x107e97ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff89e86000 -     0x7fff89f52fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff8ca52000 -     0x7fff8ca6dff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff8e8e3000 -     0x7fff8e994fff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff9181e000 -     0x7fff91826fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff93f18000 -     0x7fff94101fff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff94d88000 -     0x7fff94d9dff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff94ed9000 -     0x7fff94edcff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff94f3d000 -     0x7fff94f5fff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
    Any suggestions and help apprecieated.
    --Dan

    Dan Bratten wrote:
    3/10/13 7:48:27.128 PM com.apple.backupd[20992]: Backup completed successfully.
    3/10/13 7:48:27.000 PM kernel[0]: Sandbox: sandboxd(21005) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:50:27.573 PM mdworker[21015]: Unable to talk to lsboxd
    3/10/13 7:50:27.577 PM mdworker[21014]: Unable to talk to lsboxd
    3/10/13 7:50:27.622 PM sandboxd[21016]: ([21015]) mdworker(21015) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.626 PM sandboxd[21016]: ([21014]) mdworker(21014) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.000 PM kernel[0]: Sandbox: sandboxd(21016) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:52:28.404 PM mdworker[21026]: Unable to talk to lsboxd
    3/10/13 7:52:28.408 PM mdworker[21027]: Unable to talk to lsboxd
    3/10/13 7:52:28.457 PM sandboxd[21028]: ([21026]) mdworker(21026) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.461 PM sandboxd[21028]: ([21027]) mdworker(21027) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.000 PM kernel[0]: Sandbox: sandboxd(21028) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 10:04:58.000 PM bootlog[0]: BOOT_TIME 1362978298 0
    3/10/13 10:05:24.000 PM kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    3/10/13 10:05:24.000 PM kernel[0]: vm_page_bootstrap: 3994120 free pages and 167416 wired pages
    3/10/13 10:05:24.000 PM kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
    3/10/13 10:05:24.000 PM kernel[0]: zone leak detection enabled
    3/10/13 10:05:24.000 PM kernel[0]: standard timeslicing quantum is 10000 us
    3/10/13 10:05:24.000 PM kernel[0]: standard background quantum is 2500 us
    3/10/13 10:05:24.000 PM kernel[0]: mig_table_max_displ = 74
    3/10/13 10:05:24.000 PM kernel[0]: corecrypto kext started!
    3/10/13 10:05:24.000 PM kernel[0]: Running kernel space in FIPS MODE
    You have a common problem with OS X 10.8.2, the "unable to talk to lsboxd" message. First of all, try to fix this. It's fixed just starting your Mac in safe mode, holding the Shift key while your computer is starting. Then, just after starting in safe mode, restart, and that message will disappear. Finally, see if your red message appears

  • Sandboxd WebProcess deny mach-lookup ATS Query

    Hi
    I keep getting a lot of these lines on the system log messages (Lion 10.7.3)
    Anyone has an idea what doest it mean?
    Thanks
    13/03/12 13:50:58,285 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 975
    13/03/12 13:50:58,285 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4033
    13/03/12 13:50:58,286 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4125
    13/03/12 13:50:58,286 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4202
    13/03/12 13:50:58,286 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4477
    13/03/12 13:50:58,287 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4767
    13/03/12 13:50:58,321 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 975
    13/03/12 13:50:58,321 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4033
    13/03/12 13:50:58,321 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4125
    13/03/12 13:50:58,322 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4202
    13/03/12 13:50:58,323 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4477
    13/03/12 13:50:58,356 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4767
    13/03/12 13:50:58,381 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 975
    13/03/12 13:50:58,382 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4033
    13/03/12 13:50:58,382 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4125
    13/03/12 13:50:58,383 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4202
    13/03/12 13:50:58,383 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4477
    13/03/12 13:50:58,384 sandboxd: ([5444]) WebProcess(5444) deny mach-lookup ATS Query Port 4767

    Although I'm not a software engineer, I've done some research on this...
    This is a common entry type
    WebProcess is trying to accerss a mach service, a component of the oepertaing system
    Sandbox(ing) is a design concept for software, which should help apps be more stable & make it harder for malware ( viruses, et al ) to hijack an app for potentially nefarious purposes
    So the operating system is informing the software developers, in this case @ Apple, that WebProcess is attempting to access something that it either shouldn't or needs to be given the correct permissions to access
    There is nothing wrong with your computer.  This is a tool to help developers find where holes exist in their sandboxed apps.  There is nothing that you can do to fix this & it shouldn't cause any performance issues
    WebProcess is a separate process from Safari.  Basically, Safari is the user interface to the browser & WebProcess is the web page.  Because it is usually the web page that causes crashes, Safari & WebProcess run independently of each other.  This way, when WebProcess crashes, it won't take down Safari.  Rather than rebooting the whole app, WebProcess needs only refresh the open tabs

  • Problem: mdworker(20190) deny mach-lookup com.apple.ls.boxd

    Hey guys,
    since a while now, the macbook pro freeze and the mouse switch to this cycle (using firefox)...
    Here are the entries of the console after the freeze.
    08.12.12 12:40:16,467 sandboxd[20205]: ([20190]) mdworker(20190) deny mach-lookup com.apple.ls.boxd
    mdworker(20190) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [20190]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x10399d000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [447]
    Date/Time:       2012-12-08 12:40:16.346 +0100
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   CoreFoundation                    0x00007fff8ec8d803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                    0x00007fff8ec92ee6 __CFRunLoopRun + 1078
    3   CoreFoundation                    0x00007fff8ec926b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                    0x00007fff8eca1371 CFRunLoopRun + 97
    5   mdworker                          0x00000001039a5ba9
    6   libdyld.dylib                     0x00007fff852b97e1 start + 0
    Thread 1:
    0   libsystem_c.dylib                 0x00007fff85220eeb tiny_free_list_add_ptr + 378
    1   libsystem_c.dylib                 0x00007fff85219f12 szone_free + 2094
    2   libdispatch.dylib                 0x00007fff8da48695 _dispatch_cache_cleanup + 30
    3   libdispatch.dylib                 0x00007fff8da4a0ba _dispatch_mgr_thread2 + 61
    4   libdispatch.dylib                 0x00007fff8da49afd _dispatch_mgr_invoke + 134
    5   libdispatch.dylib                 0x00007fff8da499ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib            0x00007fff842706c2 semaphore_wait_trap + 10
    1   libxpc.dylib                      0x00007fff82ff5e1f xpc_connection_send_message_with_reply_sync + 127
    2   LaunchServices                    0x00007fff8db033ce send(LSBoxMessage&, LSBoxMessage&) + 28
    3   LaunchServices                    0x00007fff8db83d4b lsbox_preflightAppLaunch + 84
    4   LaunchServices                    0x00007fff8db0e341 _LSFindOrRegisterBundleNode + 857
    5   LaunchServices                    0x00007fff8db6ab02 _LSRegisterNode + 75
    6   LaunchServices                    0x00007fff8db16a0f _LSBundleCopyOrCheckNode + 1047
    7   LaunchServices                    0x00007fff8dafe5b6 _LSCopyLibraryItemURLs + 486
    8   mdworker                          0x00000001039cd014
    9   libdispatch.dylib                 0x00007fff8da4af01 _dispatch_call_block_and_release + 15
    10  libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    11  libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    12  libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    13  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    14  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    15  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   liblaunch.dylib                   0x00007fff848e37c4
    2   liblaunch.dylib                   0x00007fff848e24d9 bootstrap_look_up3 + 69
    3   libxpc.dylib                      0x00007fff82ff3c21 _xpc_connection_bootstrap_look_up_slow + 371
    4   libxpc.dylib                      0x00007fff82ff2c82 _xpc_connection_init + 1062
    5   libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    6   libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    7   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    8   libdispatch.dylib                 0x00007fff8da48448 _dispatch_queue_drain + 180
    9   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    10  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    11  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    12  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Binary Images:
           0x10399d000 -        0x1039f6ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff82fea000 -     0x7fff8300cff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
        0x7fff84260000 -     0x7fff8427bff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff848e0000 -     0x7fff848e8fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff851ea000 -     0x7fff852b6fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff852b7000 -     0x7fff852baff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8da45000 -     0x7fff8da5aff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8dafa000 -     0x7fff8dbabfff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff8ec5e000 -     0x7fff8ee47fff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    ================================================================================ ================================
    08.12.12 12:40:16,529 sandboxd[20205]: ([20189]) mdworker(20189) deny mach-lookup com.apple.ls.boxd
    mdworker(20189) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [20189]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x106809000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [113]
    Date/Time:       2012-12-08 12:40:16.468 +0100
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   CoreFoundation                    0x00007fff8ec8d803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                    0x00007fff8ec92ee6 __CFRunLoopRun + 1078
    3   CoreFoundation                    0x00007fff8ec926b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                    0x00007fff8eca1371 CFRunLoopRun + 97
    5   mdworker                          0x0000000106811ba9
    6   libdyld.dylib                     0x00007fff852b97e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib            0x00007fff84272d16 kevent + 10
    1   libdispatch.dylib                 0x00007fff8da499ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib            0x00007fff84272d16 kevent + 10
    1   libdispatch.dylib                 0x00007fff8da489ee _dispatch_mgr_wakeup + 16
    2   libdispatch.dylib                 0x00007fff8da47e65 _dispatch_wakeup + 28
    3   libdispatch.dylib                 0x00007fff8da47e10 _dispatch_queue_push_list_slow2 + 33
    4   libdispatch.dylib                 0x00007fff8da47ecd _dispatch_wakeup + 132
    5   libdispatch.dylib                 0x00007fff8da48027 _dispatch_resume_slow + 17
    6   libxpc.dylib                      0x00007fff82ff5ff2 _xpc_connection_listen_for_reply + 198
    7   libxpc.dylib                      0x00007fff82ff5eff _xpc_connection_send_message_with_reply_f + 136
    8   libxpc.dylib                      0x00007fff82ff5e10 xpc_connection_send_message_with_reply_sync + 112
    9   LaunchServices                    0x00007fff8db033ce send(LSBoxMessage&, LSBoxMessage&) + 28
    10  LaunchServices                    0x00007fff8db83d4b lsbox_preflightAppLaunch + 84
    11  LaunchServices                    0x00007fff8db0e341 _LSFindOrRegisterBundleNode + 857
    12  LaunchServices                    0x00007fff8db6ab02 _LSRegisterNode + 75
    13  LaunchServices                    0x00007fff8db16a0f _LSBundleCopyOrCheckNode + 1047
    14  LaunchServices                    0x00007fff8dafe5b6 _LSCopyLibraryItemURLs + 486
    15  mdworker                          0x0000000106839014
    16  libdispatch.dylib                 0x00007fff8da4af01 _dispatch_call_block_and_release + 15
    17  libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    18  libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    19  libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    20  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    21  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    22  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib            0x00007fff84270686 mach_msg_trap + 10
    1   liblaunch.dylib                   0x00007fff848e37c4
    2   liblaunch.dylib                   0x00007fff848e24d9 bootstrap_look_up3 + 69
    3   libxpc.dylib                      0x00007fff82ff3c21 _xpc_connection_bootstrap_look_up_slow + 371
    4   libxpc.dylib                      0x00007fff82ff2c82 _xpc_connection_init + 1062
    5   libdispatch.dylib                 0x00007fff8da470b6 _dispatch_client_callout + 8
    6   libdispatch.dylib                 0x00007fff8da4847f _dispatch_queue_drain + 235
    7   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    8   libdispatch.dylib                 0x00007fff8da48448 _dispatch_queue_drain + 180
    9   libdispatch.dylib                 0x00007fff8da482f1 _dispatch_queue_invoke + 52
    10  libdispatch.dylib                 0x00007fff8da481c3 _dispatch_worker_thread2 + 249
    11  libsystem_c.dylib                 0x00007fff85200cab _pthread_wqthread + 404
    12  libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib            0x00007fff842726d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                 0x00007fff85200cb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                 0x00007fff851eb171 start_wqthread + 13
    Binary Images:
           0x106809000 -        0x106862ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff82fea000 -     0x7fff8300cff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
        0x7fff84260000 -     0x7fff8427bff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff848e0000 -     0x7fff848e8fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff851ea000 -     0x7fff852b6fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff852b7000 -     0x7fff852baff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8da45000 -     0x7fff8da5aff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8dafa000 -     0x7fff8dbabfff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff8ec5e000 -     0x7fff8ee47fff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    ================================================================================ ================================
    08.12.12 12:40:16,000 kernel[0]: Sandbox: sandboxd(20205) deny mach-lookup com.apple.coresymbolicationd
    Maybe some of you might know an answer for this problem.
    Thanks a lot.

    baltwo wrote:
    Those are Spotlight indexing crashes, not freezes. AFAICT, theyre due to crappy sandboxing in ML. File a bug report with Apple. For more on crashes, see TN 2123 CrashReport Decipherer.
    Actually, if you look closely, you'll see that they're neither crashes (.crash) nor hangs (.hang).
    Here's what's reported in Console.app:
    1/3/2013 11:01:30.601 AM mdworker[12719]: Unable to talk to lsboxd
    1/3/2013 11:01:30.946 AM sandboxd[12721]: ([12719]) mdworker(12719) deny mach-lookup com.apple.ls.boxd
    The second line has an "attachment" icon which you can click to get the full report, which is saved in an auxiliary document at:
    /private/var/log/asl/AUX.2013.01.03/796282
    Here's the contents (minus the backtrace information) of that asl (Apple System Log) auxiliary document:
    mdworker(12719) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [12719]
    Path:        /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x10817a000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [340]
    Date/Time:       2013-01-03 11:01:30.905 -0500
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Compare that with a crash log (.crash) which specifies a Crashed Thread number as well as the Exception Type and Exception Codes:
    Process:         AppleScript Editor [88791]
    Path:            /Applications/Utilities/AppleScript Editor.app/Contents/MacOS/AppleScript Editor
    Identifier:      com.apple.ScriptEditor2
    Version:         2.5 (138)
    Build Info:      ScriptEditorX-138000000000000~5
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [344]
    User ID:         501
    Date/Time:       2013-01-01 06:05:30.986 -0500
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Crashed Thread:  8
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffff8
    So, it's not a crash, but just a report of a sandboxing violation. It is likely the backtrace information that makes it look so similar to a crash, but the backtrace information serves the same purpose in both cases: to provide the contextual information about what lead up to the event being reported. (In the case of a crash log, there will be one Thread that is listed as Crashed).
    Anyway, if it isn't already obvious, I'm experiencing the same logging to Console about this issue, and a Google search led me here.
    From what I've gathered, you can apparently fix the issue by restarting in Safe Mode, then restarting normally. That appears to delete some cache files inside the "secure" temporary items and caches folders, which are located in /private/var/folders/, that are somehow responsible for this issue.
    Unfortuanately, I don't think I can start up in Safe Mode, since I don't have a recovery partion, because my Mountain Lion installation is spread across 2 volumes in a RAID 0 setup.
    I'm still in the process of researching this, and need to reboot now to try creating an external flash drive with a ML installation + Recovery Partition.

  • Mdworker deny mach-lookup com.intego.mig_hook (pre-ls-info fstype:hfs

    I made a clean insatlle of Mouatin Lion and my HD is  is filled with many files every day.
    I looked in the console, I get this message that reproduces to infinity
    Here you have an example :
    mdworker(2557) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:240000004C diag:0 uti:com.apple.property-list plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 1387774)
    Process:         mdworker [2557]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x10e999000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [305]
    Date/Time:       2012-10-06 13:27:46.816 +0200
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   CoreFoundation                          0x00007fff8bb05803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                          0x00007fff8bb0aee6 __CFRunLoopRun + 1078
    3   CoreFoundation                          0x00007fff8bb0a6b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                          0x00007fff8bb19371 CFRunLoopRun + 97
    5   mdworker                                0x000000010e9a1ba9
    6   libdyld.dylib                           0x00007fff889777e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib                  0x00007fff82ceed16 kevent + 10
    1   libdispatch.dylib                       0x00007fff8ac139ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   liblaunch.dylib                         0x00007fff861ac7c4
    2   liblaunch.dylib                         0x00007fff861ab4d9 bootstrap_look_up3 + 69
    3   liblaunch.dylib                         0x00007fff861ab591 bootstrap_look_up + 37
    4                                           0x000000010ea1eb40
    5                                           0x000000010ea1f098
    6   mdworker                                0x000000010e9a6282
    7   mdworker                                0x000000010e9a6027
    8   mdworker                                0x000000010e9a34f2
    9   libsystem_c.dylib                       0x00007fff828b8742 _pthread_start + 327
    10  libsystem_c.dylib                       0x00007fff828a5181 thread_start + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   mdworker                                0x000000010e9b5df9
    2   libsystem_c.dylib                       0x00007fff828b8742 _pthread_start + 327
    3   libsystem_c.dylib                       0x00007fff828a5181 thread_start + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff82cee6d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff828bacb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff828a5171 start_wqthread + 13
    Binary Images:
           0x10e999000 -        0x10e9f2ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff828a4000 -     0x7fff82970fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff82cdc000 -     0x7fff82cf7ff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff861a9000 -     0x7fff861b1fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff88975000 -     0x7fff88978ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8ac0f000 -     0x7fff8ac24ff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8bad6000 -     0x7fff8bcbffff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    I contacted intego France, who told me that they were not aware of this

    I contacted Intego opened a ticket (no response), but I think Version 6 must have a big bug  with ML
    you can see this url :
    https://www.facebook.com/Intego/posts/311468278907535
    dam Wallace I am getting exactly the same thing in Mountain Lion. My System Log is full of hundreds of messages repeating exactly the same thing, around 20 times per second. Macintosh.local sandboxd[7781] ([7307]): mdworker(7307) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:250000005E diag:0 uti:com.apple.application-bundle plugin:/Library/Spotlight/Application.mdimporter - find suspect file using: sudo mdutil -t 1029605)
    I think this might explain why I have been getting system freezes & kernel panics. A fix for this would be much appreciated.
    Mike Dever mdworker(2315) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:240000004C diag:0 uti:com.apple.property-list plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 64324970)

  • Error: mdworker lsboxd deny mach-lookup

    Getting the following, every 5 min, in Console.
    9/25/12 10:35:21.415 AM mdworker[503]: Unable to talk to lsboxd
    9/25/12 10:35:21.419 AM mdworker[504]: Unable to talk to lsboxd
    9/25/12 10:35:21.474 AM sandboxd[505]: ([503]) mdworker(503) deny mach-lookup com.apple.ls.boxd
    9/25/12 10:35:21.480 AM sandboxd[505]: ([504]) mdworker(504) deny mach-lookup com.apple.ls.boxd

    I'm seeing the same issue and I think it started after the 10.8.2 update on my 2012 MBP (not retina). I usually do a command-option-eject to put the machine to sleep when I leave work at night but the last three mornings when I get back to work the MBP will not wake up and I have to hold the power button to force it off. The console is full of the following messages, even during the time when it should have been sleeping:
    Sep 25 00:18:55 kernel[0]: Sandbox: sandboxd(3819) deny mach-lookup com.apple.coresymbolicationd
    Sep 25 00:20:56 mdworker[3822]: Unable to talk to lsboxd
    Sep 25 00:20:56 mdworker[3823]: Unable to talk to lsboxd
    Sep 25 00:20:56 kernel[0]: Sandbox: sandboxd(3824) deny mach-lookup com.apple.coresymbolicationd
    Sep 25 00:20:56 sandboxd[3824] ([3822]): mdworker(3822) deny mach-lookup com.apple.ls.boxd
    Sep 25 00:20:56 sandboxd[3824] ([3823]): mdworker(3823) deny mach-lookup com.apple.ls.boxd
    Also, when re-start it indexes my external Time Machine hard drive for what seems like hours - never used to do that.

  • Mdworker deny mach-lookup. But macbook won't boot in safe mode

    I have a common problem, I get theese messages every now and then in console:
    2/8/13 6:38:24.000 PM kernel[0]: Sandbox: sandboxd(793) deny mach-lookup com.apple.coresymbolicationd
    2/8/13 6:38:24.534 PM sandboxd[793]: ([791]) mdworker(791) deny mach-lookup com.apple.ls.boxd
    2/8/13 6:38:24.556 PM sandboxd[793]: ([792]) mdworker(792) deny mach-lookup com.apple.ls.boxd
    There is a solution, which should resolve it, like here https://discussions.apple.com/message/19750564?searchText=mach-lookup%20com.appl e.ls.boxd#19750564
    I have just boot in safe mode. (holding Shift during boot)
    but my macbook won't boot in Safe mode. It just freeses with a grey screen for hours and wont boot.
    I tried to leave it overnight to boot, but it didn't.
    Please help me make my macbook to boot in SafeMode.
    my configuration is the following:
    MacBookPro8,1
    OSX 10.8.2

    There is a bug in fsck_hfs that is affecting a bunch of people.  Basically as your comptuer starts in safe mode, it runs a file system check (fsck) against your hard drive, it gets to a certain point and... just sits there.  No one knows why outside of apple.
    Lots of info here, including a way to get around it by tricking the system to think fsck had been run, though the fsck will not be complete so it is not a good solution.
    https://discussions.apple.com/message/21389737?ac_cid=tw123456#21389737

  • Deny mach-lookup com.apple.PowerManagement.control

    I keep seeing this message in the Console log. In searching other discussions, I find it listed in the logs, but I don't see any explanation of whether this repesents a problem and if so how it can be fixed.
    I have already gotten rid of some of the lookup error by restarting into Safe Boot and then restarting normally.

    There is nothing wrong in terms of functionality. I did experience an intermittent loss of power on battery over the last week. I didn't make note of the exact time. I shouldn't say loss of power, but the machine would just go to sleep during use. I would click a key 10 seconds later and it would wake from sleep. Not sure if this would be related, but given: deny mach-lookup com.apple.PowerManagement.controle. it may be possible. Not sure. Besides that, no performance issues.

  • 802.1x NAC and per-user ACLs

    Can 802.1x NAC and per-user ACLs be used together on the same port? I know some of the NAC documentation says that 802.1x NAC does not support downloadable ACLs but it looks like it might be outdated and according to http://cisco.com/en/US/products/ps7077/products_configuration_guide_chapter09186a0080817284.html , it appears that there is not preventing this.
    Also, when will URL redirection to a remediation server be supported with 802.1x NAC?

    You just need to configure it differently on ACS. "Downloadable IP ACLs" used to be "Downloadable PIX ACLs" on ACS. It changed to "IP" when VPN concentrators started supporting this with ACLs too. You saw this with NAC, if I remember .. and EOU does it this way as well.
    802.1X with per-user ACLs was already shipping at the time though (has been for some time) and the mechanism is opertionally the same .. just functionally different.
    With per-user ACLs, you'd configure a VSA like:
    ip:inacl#1=deny ip any host 10.1.8.3
    ip:inacl#2=permit ip any any
    The "downloadable IP ACL" config would look like:
    deny ip any host 10.1.8.3
    permit ip any any
    In the end, both techniques use the same VSA. This VSA is 026\009\001. In "per-user-ACLs, there's no sort of handshake though to see if the ACL is already there, etc. It slaps the ACL on for you unconditionally as an authorization rule b/c you told it to. (hence the "ip:inacl" stuff above). With "downloadable", there's a handshake before actually applying the ACL .. to see if there's an earlier copy of the ACL, and it'll only update what changed, etc.
    So, it really boils down to semantics. Both techniques work. AAA config is subtely different on the backend. Look for this to get consistently deployed soon, but in the meantime, it's still supported ;-).
    Hope this helps,

  • Amount of Resources CPU and Memory per user

    Hi,
    We are looking to deploy a Line of Business Application via RemoteApp and a custom template.  The application requires a significant amount of RAM and CPU, can someone tell me who much RAM and CPUs are allocated per session \ user?  I would expect
    that we would use the Standard tier if any difference to resources available.
    Thanks
    Giles

    Hi James,
    Currently there is no way to configure resources other than selecting either Basic or Standard.  If you would like a lower per-VM user density (and thus higher resources for each user) what you can do is create more collections, and only assign
    a small number of users to each.
    For example, say you only wanted to have a maximum of 4 users on each VM, providing typically at least 1 vCPU per user.  In this case you would create collections with the Basic plan, each linked
    to the same template image, and only assign a maximum of 4 user accounts on the user access tab of each.  Assuming each user uses 80+ hours a month, the total (before discounts) cost for each collection would be $228/month, making each user
    cost about $57/month, slightly less than equivalent cost under Standard plan pricing if you factor in resources per user.
    You probably already know this, but I will explain how scaling works normally for others that may read this.  Azure RemoteApp will automatically create more VMs for each collection as needed to handle user load (Scale-Out) and shut down VMs when the
    user load is reduced (Scale-In).  The key thing that affects this scaling mechanism is the maximum concurrent users allowed on each VM, which for Standard is 10.
    In your case you are asking if you can have more resources per user, hence my instructions above for creating multiple collections and limiting the number of assigned users to less than 10 each.
    Depending on your unique needs it may make more sense to create a custom RDS deployment on Azure IaaS VMs.  In this case you could control the size/type of VM used, user density, etc.  Downside is you have to set up and manage more
    RDS components than you do if you use Azure RemoteApp.
    -TP

  • Limit the number of session per user in the Wired dot1x environment with ISE 1.2

    Hello,
    I need to check if there is any configuration/workaround to limit the number of sessions/access per user in the Wired dot1x configuration.
    I need to check if this feature is available or not to solve the following scenario:
    I have 2 SW ports configured to use dot1x authentication with ISE 1.2 server.
    If user A connects to the 1st port and authenticated then he will placed on a VLAN based on the authorization profile.
    The case, that I need to deny the same user to connect on a different machine with the same credentials.
    The ISE itself does not have this feature currently,  the only feature available is to limit the number of sessions for the guest user.
    Is there any workaround on the Cisco switches to solve this? Cisco WLC has this feature and for the VPN we can limit the number of sessions also from the ASA itself.
    Thanks.

    limit number of session per user using wired dot1x is not available in 1.3

  • Restrict access to buttons, regions, etc. on a per user basis?

    My application restricts access to buttons, regions, etc. on a per user basis.
    Here is my application logic...
    1. A User can only edit items they own.
    2. A Super-User can edit all items
    So, when a user logs in, I use a post-authentication process to set the user ID to an application level item.
    Now, for example, to have an edit button display on a page, I need to check the item's owner ID against the application level user ID...and check to see if this user is on the Super User list via a query.(which could be set to another application level item upon login...I guess)
    Question...What is the best way to do this? Conditional display? Authorization scheme?
    Would something like the following work for a Conditional Display?
    Condition: SQL Expression
    &USER_ID.=&P6_ITEM_OWNER_ID. OR USER_ID in (select USER_ID from table where USER_ID=&USER_ID.)
    How would I do this with an Authorization Scheme? (I like the idea of updating the logic in single location...but I'm not sure if it is possible because I have to check PX_OWNER_ID would be different on each page.)

    Hi Denes,
    Thanks for your code which allows user to edit (if authorized) and view (if not).
    But some how - I do not get the image to show up - instead it show a small underline.
    From SQL point of view - here is what I get - when i run the sql
    '<img src="/i/ed-item.gif">',2,CR TEST,,,,dune2.cit.cornell.edu,CRDMTEST.CIT.CORNELL.EDU,PSPROD,,,CRDMTEST
    Here is my wrap_image function
    create or replace function wrap_image(p_user_name in varchar2,p_dm_name_id in number)
    return varchar2 IS
    v boolean := False;
    ret_val varchar2(1000);
    begin
    dbms_output.put_line('user='||p_user_name);
    dbms_output.put_line('dm_name='||p_dm_name_id);
    -- Check authorization if the user is super user - return true, else if he has edit priv on dm_name_id - return true - else false
    v:=ACL_DMTOOLS_DM_PRIV(p_user_name,p_dm_name_id);
    if v then
    ret_val := '<img src="/i/ed-item.gif">';
    ret_val := ''''||ret_val||'''';
    dbms_output.put_line('TRUE');
    else
    ret_val := '';
    dbms_output.put_line('FALSE');
    end if;
    return ret_val;
    end;
    Thanks for your great educational site.
    Regards
    atul

  • Payment Distribution to Artists by per user plays, rather than total plays

    Hello!
    I just had a thought about how payment is distributed to artists that I wanted to see if anyone might have some thoughts on. Spotify still does come under criticism on occasion for artist payment distribution - I've seen a couple of instances of people citing iTunes as providing more monetary compensation to artists since it is per download, rather than per play, among other things. This seems to be especially true for independent artists, and artists who are generally less well-known.
    I was wondering if Spotify has ever considered doing payment distributions using the
         sum[ (total artist streams per user) / (total streams per user) ] across all users
    ratio for payment calculation, rather than the currently used
         (total artist streams across Spotify) / (total streams across Spotify)
    approach, i.e. calculating the artists' play ratio by user, rather than in one giant pool. If you have considered this, I would love to hear why the current payment implementation was chosen rather than a per user method, such as the one listed above. But... 
    If a per user method has not been considered by Spotify previously, I think it would be nice - while I'm not an analyst myself, I imagine that it could lead to more revenue for independent artists, and maybe even less famous artists that are still beholden to rights owners for distribution of payment. I think it would do this because it could account for differences in number of plays per user - rather than users who tend to play more music over the course of a month contributing more all artists' payout, each user has an equal voice in how money gets distributed to artists.
    I understand that such a switch would be difficult, and possibly insurmountable in the instance of free users - so, I am positing this as an idea not for all users, but for Premium users only. With Premium, it is a feasible goal, since you have a finite number of plays, and a finite amount of money coming directly from that user, and do not have to worry about trying to calculate differences in advertisement impact for different users. Doing that ratio calculation would be relatively straightforward of a switch computationally (though quite a large change in the system nonetheless, of course). 
    I think this type of change would empower both users and artists to use Spotify more. Firstly, it would empower artists to allow Spotify to play their music because the metrics they would get per month would be more reflective of the size of their fan base, and how much importance that fan base puts on the artists' music than current metrics.
    Secondly, it would empower users more, which I think is especially important for users between 18-32 years of age. While I am not an expert on the subject, I often find that users in this age group (my age group) care a great deal about having control over where their money ends up, which in this case means knowing which rights holders and/or artists are getting the money they are spending. I know I do. Switching to this system, while still not addressing the injustices that are felt within the relationship between rights holders and artists by many, would still allow users to have more of a say in who gets their money than the current system. On top of that, it might be helpfult for Spotify itself - if using Premium is the only way for users to feel empowered by knowing how their money is distributed, it may encourage people in the free tier to upgrade to Premium in order to feel empowered.
    Just a thought. I'd love to hear what you and others have to say about this idea. 

    @Merik thanks for the warm welcome, and for the quick, informative response!
    I had the chance to take a look at that page you linked to before my original post, and saw that paragraph you quoted, as well as the bullet point about paid users having a higher "per stream" rate. I guess what I was more interested in (and perhaps this is not the right place to ask this question?) was if there was more of an in-depth "why" behind their decision (and thanks again for linking to it!) documented anywhere that I might be able to read more about. Maybe I was missing something on that page (and please let me know if so!), but the only "why" that I could find was a sentence in the paragraph you quote above:
    "We believe, however, that our service and the lives of artists will both be best if the World’s music fans enjoy more music than ever before in a legal, paid manner".
    While it's great to see their opinion, I was more curious about the line of reasoning behind that position is all. Because I do wonder whether empowering premium users to have more fine-grained control over how their money is allocated, such as by doing pay "per user", might lead to both more paid users and more revenue for independent and/or lesser-known artists - and if that's something that Spotify has researched already, I would love to hear more about the pros and cons behind such an approach!
    Thanks!

Maybe you are looking for

  • Dynamic queries in report builder 6i ( ref cursor query )

    Hi everyone, My requirement is that I want to create a report where the query is dynamic. The dynamic part will be known at runtime as it is being passed via a parameter. My query looks like this : select * from emp where sal :p1 :p2 Possible values

  • 3.0.02 EA1 - Edit table data in a grid

    Editing table data in a grid is broken in 3.0.02 EA1 under Windows XP Pro SP3 Bug #1: When not in editing mode the cursor keys must move the focus from a cell to cell. Instead an edit mode is activated Bug #2: There is no way to leave cell edit mode

  • Monitoring via 2nd / external monitor

    Is there a way to have playback to a second / external monitor? It seems like an obvious feature for an on-set tool, but I can't seem to find it. I have one monitor facing me with the main program controls, and a second monitor which would face the c

  • Authorizations in search resalt PO

    Hi all, Please help me. I have two transaction type PO: ECPO and ECMO. ECPO - company 1, ECMO - company 2. When I in BBP_POC see Search result I see both transaction type. But I need that if user company 1, then at search result was  only the ECPO ty

  • I lost my connection with my AirPort Base Station when I upgraded to the OS Maverick.  How can I get my system to recognize the base station again?

    I lost my connection with my AirPort Base Station when I upgraded to the OS Maverick.  I can still see the Internet, but the Time Machine cannot backup now because it cannot locate the AirPort base station.  How can I resolve this issue? Steps alread