My problem with Intermapperd is the amount of CPU consumed. Currently running traditional on a 1.8GHz iMac G5, monitoring 529 devices. This uses 35 - 40 % CPU time. (there are lots of duplication and poor mapping we have found with the lists from 4.3 - thanks guys - which we are slowly addressing)
Running the Daemon used 90%+ CPU leaving nowt for local console. Is this normal or have we stuffed something up?? Regards, Justyn Phillips VMS Systems Administrator Infomedia Ltd 357-373 Warringah Road Frenchs Forest NSW 2086 Australia Phone + 61 (0)2 9454 1500 Direct + 61 (0)2 9454 1761 Mobile + 61 (0)412 288 320 Fax + 61 (0)2 9454 1888 [EMAIL PROTECTED] www.infomedia.com.au * This email transmission and any attachments may contain privileged and confidential information. If you are not the intended recipient you are not authorised to, read, distribute or reproduce any part of this transmission (including any attachments) without the prior written consent of the sender. If you have received this email in error, please notify the sender by email immediately. * Opinions expressed in this email and any attachment are those of the sender and not necessarily the opinions of Infomedia. * Please scan this email and any attachment for viruses. Infomedia takes all reasonable precautions to ensure no viruses are present in this email or accompanying attachments, but does not under any circumstance accept any responsibility for loss or damage caused by viruses. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, 9 June 2005 1:43 AM To: InterMapper Discussion Subject: [IM-Talk] Traditional installation procedures Rich Brown wrote: > >We plan to maintain feature parity with the server portion of >InterMapper Traditional for the forseeable future. > > >Even if you continue to use Traditional, you can use this version of >Console to get the new GUI features. Rich, As you know I am one of your customers who has not switched to using Intermapperd with Console/Remote because the aesthetics and functionality are not quite there yet. The new installation procedures (relegating Intermapper Traditional to the Extras folder) causes problems for Traditional customers. The problem is that if we want Console to get the new GUI features we have to double click the Intermapper-4.3.pkg. Doing this stops the Traditional Intermapper server (without asking!) and starts Intermapperd (which is almost impossible to kill on Tiger unless you know where the magic Stop.sh program is). Traditional users require an installation procedure that is independent of Intermapperd until such time as we can switch to using Intermapperd. Given that you plan to maintain feature parity for the foreseeable future, why not have a third column on your http://www.intermapper.com/binaries/index.html page entitled "Intermapper Traditional". We have a number of Intermapper licenses and a number of different people install Traditional besides myself at our site, and the current installation procedures are causing problems. I need a one click installation procedure like before. Thanks Dennis O'Reilly University of British Columbia ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED] ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
