InterMapper FAQs

How can I stop the InterMapper server from polling for a while?

The easiest way to stop InterMapper's polling for a while is to disable all the maps. To do this:

  1. Open the Server Settings... window
  2. Click the Enabled Maps tab.
  3. Uncheck all the maps. They will no longer be polled or tested.

Alternatively, you can disable maps individually from the Map List by right-clicking on a map in the list and selecting the ‘Disable’ command.

How can I stop the InterMapper server? How can I restart it?

On MacOS X, InterMapper installs a Menu Bar Application that gives a summary of InterMapper's status, and allows you to start and stop the InterMapper daemon.

On Windows, InterMapper installs an icon in System Tray (lower right corner) that does much the same thing.

On all Unix/Linux installations, InterMapper installs a script to control the server daemon.

We recommend you read the Readme file on the Downloads page for information specific to your version.

How can I move InterMapper from one server to another?

The recommended way to move InterMapper to another server is to follow these steps:

  1. Install InterMapper on the new server, and stop the InterMapper service/daemon when installation is complete.
  2. Stop the InterMapper service/daemon on the old server and copy your InterMapper Settings folder to the new platform, replacing the one created when you installed InterMapper on the new server.
  3. On the new server, start the InterMapper service/daemon.

The default location for the  InterMapper Settings folder depends upon the platform where installed:

 

Note: If you are migrating from  Mac OS X PowerPC to Mac Intel, Windows or any other Intel-based system; or from Solaris Sparc to Solaris Intel, please contact support@dartware.com prior to installing on the new platform. Additional steps are necessary in order to preserve the historical chart data when migrating between these platforms.

How can I uninstall the InterMapper server?

Each version of InterMapper comes with its own uninstaller. Find the original distribution file (or retrieve the current version from http://www.dartware.com/files) and use its uninstall feature. 

I get an "intermapperd dead but subsys locked" error message when I get InterMapper status by typing "/etc/init.d/intermapperd status". What does this mean?

The message "intermapperd dead but subsys locked" means that  intermapperd is not running; the daemon has either crashed or was sent an explicit kill command by the root user. Furthermore, the InterMapper lock file /var/lock/subsys/intermapperd exists when intermapperd isn't running.

To restart InterMapper, log on to the system as root and type:

  /etc/init.d/intermapperd restart

You may also clear the lock file by typing:

  rm /var/lock/subsys/intermapperd

but this isn't required because the restart command does this.

 

Why do I have trouble with Telnet using my Windows terminal program?

Q: When I use HyperTerminal to telnet into InterMapper's server, I don't see character echoes. Why not?

A: Two commonly-available Windows telnet clients, HyperTerminal and the command-line telnet client, do not work correctly with InterMapper in their default configuration. Neither of them do local echoing by default, and both refuse to turn it on when asked to do so by the InterMapper server.

Therefore, neither of these clients work out-of-the-box with InterMapper, so you need to turn on local echoing yourself.

Turning On Local Echoing in HyperTerminal

With your InterMapper session loaded, choose File->Properties. Click the Settings tab. Click the ASCII Setup... button. Check the box labelled "Echo typed characters locally". When connecting to earlier versions of InterMapper, you should also check the box labelled "Send line ends with line feeds". Later versions of InterMapper do not require this (although it won't hurt.) Click Ok to close the ASCII Setup dialog, then click Ok to put away the Properties dialog. Remember to save your session to make the new settings permanent.

Turning On Local Echoing with Built-in Telnet Client

Start your telnet session with InterMapper. Press Ctrl+] to enable the client to process setup commands. Type "SET LOCAL_ECHO" and press Enter to turn on local echoing. Press Enter again to return to your session. I'm not aware of any way to save this setting for future sessions, so you'll need to do this each time.

Putty - Another Choice

One free Windows telnet client we have had good luck with is Putty. Putty is available at http://www.chiark.greenend.org.uk/~sgtatham/putty/.  Putty requires no configuration to work correctly with InterMapper. You may find this nicer to use than either of the built-in options that come with Windows.

On an Xserve, can I use the serial port for paging?

You can use the built-in serial port to drive an external modem that can in turn send page notifications. To do this, you must disable the getty process that's usually listening on that port.

On the Xserve, open this file:

/System/Library/StartupItems/SerialTerminalSupport 

At about line 72 is:

ENABLE_SERIAL_TERMINAL=$TRUE 

Change this to:

ENABLE_SERIAL_TERMINAL=$FALSE 

Re-init the system, and there should be no getty and InterMapper will get to the modem just fine. (Thanks to Charlie Winchcombe for this tip.)