Automatically start-up FMServer at boot

[strippi]

Yes, still troubles!

I hope Filemaker Inc. (100% owned by Apple Computer Inc.)

will improve ASAP its FMServer5.5 for X

I would like for example a "startup at boot" checkbox (just like a lot of other services)

But at the moment what I really need is the solution to this problem: start up FMServer at boot without login and control what files it must open.

Now I've installed FMServer onto a G4 Dual800 running MacOS X Server 10.1.1

Last weekend I read in different forums the same suggestion:

"Create a FMPServer folder into StartupItems and so on..."

Taking a look in deep I discovered two different StartupItems folders:

the first in /Library, the other in /System/Library/ so I'm a bit confused.

The real problem is that even if the shell FMPserv is executable

(by everyone) and the .plist is readable (by everyone) I'm not able to read

the ConsoleMessage and the folder with these files is copied in both

the StartupItems folders and the /etc/hostconfig is well configured,

I'm not able to run FMServer5.5 at startup at all!!!

I'm not able to read the ConsoleMessage "Starting FileMaker Pro Server "

too....

So, is there a "wait statement" I can put after the ConsoleMessage?

just for seeing if the shell is executed in the right manner?

Are there some differences between MacOS X and MacOS X Server?

infact I'm running FMServer 5.5 on a G4 w/MacOS X Server 10.1.1.

Since I'm not able to see what I desire, I put you also this question:

How can I specify the files to be opened? I saw that there are more than one fmserverd -one for each hosted file?- and even if I quit the FMserver Config app, still the files are being hosted.

Any help/suggestion/caveat will be appreciated a lot.

Thank You very much in advance,

/Steve

[bionicjay]

maybe this will help... gonna try this myself

quote:

---

Date: Tue, 6 Nov 2001 15:49:36 -0600

From: Jon Gardner

Subject: Automatic startup of FileMaker Pro Server 5.5 on Mac OS X

FileMaker Pro Server 5.5 on Mac OS X won't startup automatically when the machine boots. According to the documentation and FileMaker technical support, the only way to start the so-called "server" is to run the FileMaker Server Config app and click the "Start" button. Since this is totally lame and unacceptable, I devised a workaround.

1. Logon as root.

2. Edit /etc/hostconfig and add the following line somewhere in the file: FMPSERVER=-YES-

3. In /Library/StartupItems, create a new directory named "FMPServer".

4. In the FMPServer directory, create two files, one named "StartupParameters.plist" and the other named "FMPServer".

Contents of StartupParameters.plist:

--------------------------------------------------

{

Description = "FileMaker Pro Server";

Provides = ("FMPServer");

Requires = ("Resolver");

OrderPreference = "None";

Messages =

{

start = "Starting FileMaker Pro Server";

stop = "Stopping FileMaker Pro Server";

};

}

--------------------------------------------------

Contents of FMPServer:

--------------------------------------------------

#!/bin/sh

. /etc/rc.common

##

# Start up FileMaker Pro Server

##

if [ "${FMPSERVER:=-NO-}" = "-YES-" ]; then

ConsoleMessage "Starting FileMaker Pro Server"

# If the FileMaker Server 5.5 folder is in a different location

# from the one shown below, modify the path appropriately!

cd "/Applications/FileMaker Server 5.5/FileMaker Server

Config.app/Contents/Resources/"

./fmserverd start -c fmserver.conf

fi

[The script, as received, contained the line ".. /etc/rc.common", likely due to the email transport system's dislike of lines that begin with a period. We believe that ". /etc/rc.common" is what the author intended.