[Box-Admins] Re: squeaksource.com image update (was: Does source.squeak.org have the socket leak problem?)

[Chris Muller]

On Fri, Oct 18, 2013 at 12:59 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> At this point, the SqueakSource code in our squeaksource.com image
> should be identical to that of our source.squeak.org image. If I fix
> anything, I'll certainly commit the changes, but someone else fixed the
> socket leak problem and all I did is get squeaksource.com updated to take
> advantage of those fixes.

What are those fixes?  I would like to ensure they're part of the
new-trunk SS image at box4.squeak.org:8888.

> I know you are also working on the updates for source.squeak.org, and what
> I'd like to do if you agree is be a "close follower" of that work. When
> the source.squeak.org update goes live, I would like to apply the
> identical updates to our squeaksource.com image shortly afterwards. Does
> that make sense?
>
> Dave
>
>> Dave, did you happen to merge the latest versions of SqueakSource
>> packages hosted at source.squeak.org into your new server for
>> SqueakSource.com?
>>
>> Also, would you please commit back any additional fixes you made
>> (e.g., socket leak problem?) to same repository?
>>
>> Thanks.
>>
>> On Thu, Oct 17, 2013 at 7:56 AM, David T. Lewis <lewis at mail.msen.com>
>> wrote:
>>> On Sun, Oct 13, 2013 at 05:34:11PM -0400, David T. Lewis wrote:
>>>>
>>>> The new squeaksource image seems to be running well. It is too early to
>>>> say
>>>> for sure, but the runaway socket leaks that I saw in the old image do
>>>> not
>>>> appear to be occurring in the new image. There is however one socket
>>>> leak
>>>> that I have found to be associated with the VNC server. This apparently
>>>> leaves one open file descriptor when a client closes its connection
>>>> (BYW,
>>>> this is the first time I've really had occasion to use Ian's RFBServer,
>>>> it
>>>> is really quite amazing). This does not directly impact
>>>> squeaksource.com
>>>> stability so I'm not going to worry about it for now.
>>>
>>> To follow up - the new squeaksource.com image has continued to run
>>> without
>>> problems since I wrote the above. I intentionally restarted it two days
>>> ago
>>> (testing signal handlers for SIGHUP and SIGTERM based on suggestion from
>>> Chris), but otherwise it has run reliably and no manual intervention has
>>> been needed.
>>>
>>> The socket leak problem is resolved, aside from the minor VNC bug
>>> mentioned
>>> above, and there has been no recurrence of the unexplained system
>>> overload
>>> that had occurred one time with the old image.
>>>
>>> I still need to set up squeaksource.com under daemontools (tips or
>>> examples
>>> from source.squeak.org welcome, I've never done it before). Once that is
>>> done, I expect that the squeaksource.com image can run indefinitely with
>>> little or no manual intervention.
>>>
>>> Dave
>>>
>>
>
>