>From: William C Klein <address@hidden> >Organization: Valparaiso >Keywords: 200211131551.gADFpqL24688 LDM ldmd.conf xcd_run McIDAS-XCD Bill, >From address@hidden Fri Nov 15 13: 21:38 2002 >What is the good word on the rebuild? re: The build is proceeding normally now. After it finishes, we'll see if the newly compiled code works. After the McIDAS build was done: <login as 'mcidas'> cd mcidas2002/src make clobber make all I reinstalled the distribution: make install.all and then tested the new executables to see if they still had the shared memory read problem. They don't have the problem anymore. Since the McIDAS executables appear to be OK, I restarted your LDM: <login as 'ldm'> cd ~ldm [ 1 ] > ps -u ldm PID TTY TIME CMD 25769 pts/2 0:00 tcsh [ 2 ] > ipcs IPC status from <running system> as of Fri Nov 15 15:06:52 CST 2002 T ID KEY MODE OWNER GROUP Message Queues: Shared Memory: m 0 0x50000d2f --rw-r--r-- root root m 101 0 --rw------- ldm vumcidas Semaphores: I deleted the lone ipc: [ aeolus : ldm : ~ ] [ 3 ] > ipcrm -m 101 and then removed the associated .mctmp subdirectory: [ aeolus : ldm : ~ ] [ 4 ] > ls .mctmp 101 [ aeolus : ldm : ~ ] [ 5 ] > cd .mctmp [ aeolus : ldm : ~/.mctmp ] [ 6 ] > rm -rf 101 After this cleanup, I restarted your LDM: [ aeolus : ldm : ~/.mctmp ] [ 7 ] > cd [ aeolus : ldm : ~ ] [ 8 ] > ldmadmin start starting the LDM server... the LDM server has been started Your LDM is apparently now working as it was before the reboot a couple of days ago. Tom
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.