From Newsgroup: comp.sys.mac.system

I am trying to set up IP Failover in OS X server 10.2. I want to have
scripts that will start Apple and Windows file services on ip
acquisition and stop same services on ip relinquish. I know that
IPFailover itself will trigger the scripts. I have been trying to
start and stop these services from the terminal using SystemStarter
without any luck.

I would think this would be possible because I don't want users
connecting to the Xserve after a failure. Any ideas on what I might be overlooking?

Jay
--- Synchronet 3.18b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.mac.system

In article <d9c8ca35.0307070650.30b7d670@posting.google.com>,
laslow_g@hotmail.com (jp) wrote:

I am trying to set up IP Failover in OS X server 10.2. I want to have
scripts that will start Apple and Windows file services on ip
acquisition and stop same services on ip relinquish. I know that
IPFailover itself will trigger the scripts. I have been trying to
start and stop these services from the terminal using SystemStarter
without any luck.

I would think this would be possible because I don't want users
connecting to the Xserve after a failure. Any ideas on what I might be overlooking?

You can take AppleShare down by just killing the AppleFileServer process directly. I haven't tried this on OS X Server, but it doesn't seem to
cause any problems on the client version of OS X; the preference pane
changes to reflect the new status and so on. I don't know about SMB. You
can probably get away with something similar. Give it a shot.

You might also try asking on the MacOSX-admin mailing list: http://www.omnigroup.com/developer/mailinglists/macosx-admin/

--
"First, let me make it very clear, poor people aren't necessarily killers. Just
because you happen to be not rich doesn't mean you're willing to kill."
-- George W. Bush in Washington, D.C. on May 19, 2003 --- Synchronet 3.18b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.mac.system

Thanks for the advice. I was able to get AppleShare stopped by killing the process. ps -ef | grep does not find it, but I had to use the gui Process Viewer
to find it, then find the process id, then use the terminal to kill the process.

In order to script this to run automatically during IP failover, I'm guessing some
sort of Shell Script would need to be written, and the tough part is getting the
shell script to know what PID to kill everytime, since this changes???

What is disappointing is that now I need to learn UNIX to admin this server, when one of the selling points for the Xserve was the Quartz GUI interface, which
is useless for specialized server functions. Geesh.

As far as the mailing lists, nobody has replied to any of my posts on another mailing list. Either this is really complex stuff, or it's a secret. :)

~jay

ZnU <znu@acedsl.com> wrote in message news:<znu-619529.12285607072003@news.fu-berlin.de>...

In article <d9c8ca35.0307070650.30b7d670@posting.google.com>,
laslow_g@hotmail.com (jp) wrote:

I am trying to set up IP Failover in OS X server 10.2. I want to have scripts that will start Apple and Windows file services on ip
acquisition and stop same services on ip relinquish. I know that
IPFailover itself will trigger the scripts. I have been trying to
start and stop these services from the terminal using SystemStarter
without any luck.

I would think this would be possible because I don't want users
connecting to the Xserve after a failure. Any ideas on what I might be overlooking?

You can take AppleShare down by just killing the AppleFileServer process directly. I haven't tried this on OS X Server, but it doesn't seem to
cause any problems on the client version of OS X; the preference pane changes to reflect the new status and so on. I don't know about SMB. You
can probably get away with something similar. Give it a shot.

You might also try asking on the MacOSX-admin mailing list: http://www.omnigroup.com/developer/mailinglists/macosx-admin/

--- Synchronet 3.18b-Win32 NewsLink 1.113