“can’t find” not “can find”

-- 
John Wilkes
john@wilkes.com

My life has been a series of tragedies and
triumphs, but I wouldn’t have it any other way.



> On Mar 9, 2018, at 9:42 AM, John Wilkes <john@wilkes.com> wrote:
> 
> The default, standard system shutdown kills the main surgemail process but not the swatch process? That probably explains why I can find any obviously useful information about the error in the SurgeMail crash log file.
> 
> Question for SurgeMail support: Can this be fixed in a future SurgeMail release?
> 
> -- 
> John Wilkes
> john@wilkes.com
> 
> “Learn the rules like a pro, so you can
> break them like an artist.”  -- Pablo Picasso
> 
> 
> 
>> On Mar 9, 2018, at 8:07 AM, Ed <ed@easent.net> wrote:
>> 
>> If you look for the "swatch" process after you kill the main surge process and then kill it you won't get that error.
>> 
>> We've been running on linux for years and never get that error when we kill the "swatch" process after the rest of it.
>> 
>> --Ed
>> 
>> On 03/09/2018 11:01 AM, John Wilkes wrote:
>>> Both “tellmail shutdown” and "/etc/init.d/surgemail stop” finish quickly. The init.d/surgemail method takes a little longer because the script has a 9 second delay at the end to give the SurgeMail process some time to stop cleanly.
>>> I see the same problem on a new Centos 7 installation, so it is not unique to Ubuntu. With Centos, the system shutdown process waits 5 minutes for surgemail to shutdown before giving up. I always see the “unclean “ message in SurgeMail status after rebooting, unless I manually stop SurgeMail before shutting down the system.
>> 
>> -- 
>> -----------------------------------------------------------
>> EAS Enterprises LLC
>> World Class Web and Email Hosting Solutions
>> IPv6 ready today for your needs of tomorrow!
>> Ask us about dual-stacking your site
>> www.easent.net
>> 
>