Re: [Summary-Talk] Summary 2.6.8 is now available

[John May <jmaymailing@xxxxxxxxxxxxxxxx>]

Upon further investigation, I'm not sure what happened with the
system.  I just reverted to our last working backup.  My suspicion is
that the command that installs summary service fubar-ed the system,
since I had not run Summary manually first.  Could this be possible?
Nothing else changed between when it was working and when it started
going haywire other than the 2.6.8 upgrade...

	- John


>Nothing has changed between 2.6.6 and 2.6.8 that would have any affect
>on other programs running on the same machine.
>
>Something like what you describe could happen if you ran out of virtual
>memory. Summary 2.6.8 uses the same amount of memory as 2.6.6, so I
>wouldn't expect them to behave differently. However, if you accidentally
>had both 2.6.6 and 2.6.8 running at the same time that would double the
>memory usage and that could cause the symptoms you describe.
>
>The only other possibility I can think of would be that your copy of
>Summary 2.6.8 somehow got corrupted. You could try downloading it again
>to see if that makes any difference.
>
>SSH and named would normally write error messages to the system log,
>"/var/log/system.log".
>
>Jason
>
>
>John May wrote:
>>  Something about this version is massively screwing up our OS X system
>>  when run in command-line mode.  While processing, it craps out SSH
>>  and named on the machine it's running on.  We've reverted to 2.6.6
>>  now, the previous version we had installed.
>>
>>  I looked for crash logs, but there didn't seem to be any.  Any idea
>  > on how to trace why this is occurring?

-- 

-------------------------------------------------------------------
John May : President                  <http://www.pointinspace.com>
Point In Space Internet Solutions             jmay@pointinspace.com

        Professional Lasso / PHP / MySQL / FileMaker Pro Hosting
-------------
Go to <http://summary.net/list.html> to update subscription info.