Mar 10, 2014; 11:25
Erik Vandermey - WebCentrix, Inc.
Re: DNS Deafness
Any news to report on this? I've implemented Eric's fix, but it doesn't seem to be working.
Regards,
---
Tech Support • tech@webcentrix.net • http://webcentrix.net
WebCentrix, Inc. • Web Hosting/Co-Location/Dedicated Servers • Kerio Connect/Control Reseller
On Jan 24, 2014, at 6:59 PM, Eric Knibbe <eric@lassosoft.com> wrote:
> In this case, logging out refers to the system's user account. Or does it...?
>
> Now that I know what to look for, I dug up some similar bug reports elsewhere online. Of interest:
>
> <https://issues.apache.org/bugzilla/show_bug.cgi?id=46682>
> Apache itself stops resolving if left idle for several hours. Solved by pinging Apache every 15 minutes.
>
> <http://lists.apple.com/archives/darwin-dev/2008/Jul/msg00017.html>
> <http://lists.apple.com/archives/darwin-dev/2008/Jul/msg00011.html>
> Evidence that processes started by launchd are exempt. This would explain why Lasso 9 is unaffected.
>
> <https://developer.apple.com/library/mac/documentation/Darwin/Conceptual/KernelProgramming/contexts/contexts.html>
> The article on contexts referenced above. Reading it seems to suggest that if Lasso is started by a script that is run during boot, such as the StartupItem used by Lasso 8, it will start in the startup context, which won't be flagged for garbage collection. However, if a user logs in via screen sharing (not SSH) and restarts Lasso using `lasso8ctl restart`, Lasso will be in the login context, leaving it vulnerable to DNS deafness if the user logs out, or even just closes the shell.
>
> So how to ensure a process is always started in the startup context? Besides converting the daemon to launchd, the StartupItemContext utility seems to be the answer (`man StartupItemContext`). Following Trevor's lead, I figure the proper fix is to modify line 31 of "/Applications/Lasso\ Professional\ 8/LassoAdmin/Lasso8Service.sh" to be:
>
> /usr/libexec/StartupItemContext sudo -u lasso ./Lasso8Service > /private/tmp/LassoService8.out 2>&1
>
> We can use the BootstrapDump utility (found somewhere deep within the Apple developer docs) to list each process according to its current context with `sudo ./BootstrapDump MAP`. Here's the smoking gun: if you run `sudo lasso8ctl start` without the above change, the two Lasso8Service processes appear near the bottom in the same context as your standard GUI apps. With the change, they're listed in the same context as system-level services, like httpd, WindowServer, and mDNSResponder. I'm interested in hearing if this change truly prevents DNS deafness from recurring on a Mac that's had Lasso restarted in Terminal, then logged out.
>
> One more thing. If you open a new terminal window and run `sudo lasso8ctl restart`, closing the window will warn you that the two Lasso8Service processes will be terminated. That shouldn't happen. This doesn't occur if you call lasso8ctl via the Startup Item in /Library/StartupItems/LassoPro8 using `sudo SystemStarter start "Lasso Professional 8"`, but I'm unaware of how to modify lasso8ctl or Lasso8Service.sh to have the Terminal truly disown the Lasso8Service processes. Any solutions, please share.
> ‐‐‐‐‐‐‐‐‐‐✂‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
> Eric3
>
>
> On 2014-01-23, at 12:47 PM, Gary Zasuwa wrote:
>
>> Log out of the Lasso siteadmin or serveradmin panels?
>>
>> Sincerely,
>>
>> Gerard Zasuwa Gary
>> Ld Systems Analyst
>> Henry Ford Health System
>> Greenfield Health Systems
>> (313) 916-2651 work
>> (313) 585-9621 NEW CELL
>>
>>
>> On Jan 23, 2014, at 11:11 AM, French, Shelane wrote:
>>
>>> Anecdotal evidence: maybe the reason I never experienced this problem with
>>> my 8.5 OS X installation is that we don't log out. It runs the server OS
>>> in a rack mount in our data center, so no need for us to log out.
>>>
>>> I hope this was the answer for everyone who has suffered this issue.
>>>
>>> On 1/22/14 8:44 PM, "Sean Stephens" <sean@lassosoft.com> wrote:
>>>
>>>>
>>>>> If it does turn out to be the issue - I think we all owe Trevor a drink
>>>>> or two.
>>>>
>>>>
>>>> If it does turn out to be the case, I'll be the first in line. We've
>>>> poured more than a few drinks on that issue over the past decade, I'll
>>>> happily personally pour one more.
>>>>
>>>> (Might have to buy Rasmus a drink too)
>>>>
>>>> Sean Stephens
>>>> CEO
>>>> LassoSoft Inc.
>>>> http://www.lassosoft.com
>>>>
>>>> #############################################################
>>>> This message is sent to you because you are subscribed to
>>>> the mailing list Lasso Lasso@lists.lassosoft.com
>>>> Official list archives available at http://www.lassotalk.com
>>>> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
>>>> Send administrative queries to <Lasso-request@lists.lassosoft.com>
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso Lasso@lists.lassosoft.com
>>> Official list archives available at http://www.lassotalk.com
>>> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
>>> Send administrative queries to <Lasso-request@lists.lassosoft.com>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso Lasso@lists.lassosoft.com
>> Official list archives available at http://www.lassotalk.com
>> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
>> Send administrative queries to <Lasso-request@lists.lassosoft.com>
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso Lasso@lists.lassosoft.com
> Official list archives available at http://www.lassotalk.com
> To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
> Send administrative queries to <Lasso-request@lists.lassosoft.com>
#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso Lasso@lists.lassosoft.com
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>