That did it, sorta. Going the rename route did some really weird things with
permissions. Got it sorted though, thanks!
On 11/30/14 11:56 AM, surgemail-support wrote:
> I think the problem is that since you didn't start by running an install it
> never did the extra step of setting up the startup scripts as it doesn't
> need to do that on an 'update'.
> To force it do do that you could 'rename surgemail.ini' run the install,
> then stop surgemail and rename your real surgemail.ini back.
> Or use whatever manual method you prefer to add
> /usr/local/surgemail/surgemail_start.sh to the system startup scripts
> Either method should be fine.
> I got to *ahem* unexpectedly move my Surgemail installation from one Mac
> OSX boxen to another. Everything went swimmingly except one little
> thing, Surgemail isn't starting itself automatically on a system reboot.
> I can come up with a couple ways to do this already, but since I didn't
> have this problem on my old system/install I'm guessing I shouldn't have
> this problem on my new system/install.
> To move my system I copied /var/surgemail, /usr/local/surgemail and
> /etc/surgemail.ini to the new machine. I also corrected the permissions.
> Then I downloaded the latest current and installed it and it saw it as
> an upgrade which was fine and it's starts fine when I manually start it
> as ./surgemail.
> sh-3.2# ./surgemail
> Changing to run as user mail as no '-nosetuid' switch found
> call do_fake_start
> Startmail starting surgemail using configuration file /etc/surgemail.ini
> StartMail: without ipv6 compiled
> Starting surgemail as uid=502 gid=0 based on /usr/local/surgemail
> do_fake_start finished
> MAIL Running - Home /usr/local/surgemail - log file is
> Detaching server process
> Does NetWin have an official recommendation on how to fix this?
Last Message | Next Message
Site Map |
Contact Netwin |
POP3 Mail Server |
Linux Webmail |
UnInstall instructions for all products
Copyright © 2017 Netwin Ltd. All rights reserved.