Let me test more tomorrow.  It was stuttering on ExecStop. Depending on 
the environment, sometime enclosing these commands in sudo does wonders. 
Plus I noted in the Surgemail_stop.sh script that the .exit and the .pid 
file are relative paths. Wonder if full path would help with the 
misbehavior I saw in ExecStop.

I also have spent a couple of days starting up SuSE servers on different 
hosting companies and the variations were enormous between hosting 
companies.  I cann't believe how badly some butchered their images.

One installed SLES 15 with no YAST, no editor of any kind(no nano, vi or 
vim even) and no ftp client.  Plus no access to any software 
repositories to add software using zypper(their rpm manager).  Obvious 
in this case, they spun up a server but never used it and as long as 
they could login, let's go with that image!

I have one on a vmware environment that seems to be working well 
enough.  But it was missing VIM & cron.  Still working through some of 
that simple crap.  Cron doesn't like not having VIM installed.  It did 
allow me to install GCC, but make was a separate package to install.  
(That one is on SuSE, imho.)

Thanks,

Lyle

On 2020-07-29 20:20, Surgemail Support wrote:
> Try this: (surgemail.service)
>
> [Unit]
> Description=SurgeMail Email
> Conflicts=sendmail.service exim.service postfix.service
>
> [Service]
> Type=forking
> PIDFile=/usr/local/surgemail/surgemail.pid
> ExecStart=/usr/local/surgemail/surgemail_start.sh
> ExecStop=/usr/local/surgemail/surgemail_stop.sh
>
> [Install]
> WantedBy=multi-user.target
>
>
> On 30/07/2020 12:52 pm, Lyle Giese wrote:
>> Does anyone have a working systemd surgemail start/stop script? I 
>> have stumbled on this and know a couple of work arounds, but my 
>> understanding of systemd is lacking...
>>
>> Thanks,
>>
>> Lyle Giese
>>
>> LCR Computer Services, Inc.
>>
>>