[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050721: New LDM installation (cont.)



>From: Nancy Selover <address@hidden>
>Organization: ASU
>Keywords: 200507190034.j6J0Ywjo000855 LDM install

Hi Nancy,

>What environment variables were supposed to be set?  My "LDM" user
>.cshrc file reads:

OK. Even more useful would be the output from:

env

However, your .cshrc file does not look strange.  As per my last
email, please send us:

- the contents of ~ldm/ldm-6.3.0/src/config.log
- the contents of ~ldm/ldm-6.3.0/src/macros.make

Thanks

Tom

># /etc/cshrc
>#
>#
>Csh configuration for all shell invocations.
>
># by default, we want this to get set.
># even for non-interactive, non-login shells.
>[ "'id -gn'" = "'id -un'" -a 'id -u' -gt 99 ]
>If $status then
>       umask 022
>Else
>       umask 002
>Endif
>
>If ($prompt) then
>  if ($?tsch) then
>       set prompt='address@hidden %c]$ '
>  else
>       set prompt=\['id -nu'@'hostname -s'\]\$\
>  endif
>
>If ( $?tsch ) then
>       bindkey "^[[3~" delete-char
>Endif
>
>Setenv MAIL "/var/spool/mail/$USER"
>
>If ( -d /etc/profile.d ) then
>       set nonomatch
>       foreach I ( /etc/profile.d/*.csh )
>         if ( -r $i ) then
>               source $i
>         endif
>       end
>       unset I nonomatch
>Endif
>Setenv LDMHOME $HOME
>Set path=($HOME/decoders $HOME.util $HOME/bin $path)
>Setenv MANPATH $HOME/man:/usr/share/man
>Setenv UDUNITS_PATH $HOME/etc/udunits.dat
>
>With the exception of the letter "i" being lowercase in the .cshrc file,
>this is verbatim. 
>
>Nancy
>
>-----Original Message-----
>From: Unidata Support [mailto:address@hidden 
>Sent: Tuesday, July 19, 2005 8:48 PM
>To: Nancy Selover
>Cc: address@hidden
>Subject: 20050719: New LDM installation (cont.)
>
>>From: Nancy Selover <address@hidden>
>>Organization: ASU
>>Keywords: 200507190034.j6J0Ywjo000855 LDM install
>
>Nancy,
>
>re: ldmadmin can't be found
>>We had the links wrong, but have fixed them.
>
>OK.
>
>>I double checked all the
>>config files to be sure I had properly edited everything, but I am 
>>getting the start-up error:
>>
>>Sh: /etc/killall: No such file or directory
>>Hupsyslog: system( "/etc/killall -HUP syslogd") returns 32512 (E.G. It 
>>didn't work.  Check that this program is setuid)
>>
>>How do I check that - what do I do?
>
>This is very strange since hupsyslog will try to run /etc/killall on SGI
>systems only.  On Linux, it should:
>
>- get the syslogd PID from the file /var/run/syslogd.pid
>- run (as 'root) 'kill -HUP syslogpid
>
>The fact that your build is trying to run /etc/killall suggests that
>there were some enviornment variable definitions in place that were
>appropriate for an SGI installation when 'configure' was run on your
>Fedora Core 3 machine.  Is it possible that you defined some environment
>variables on your FC3 machine based on experience on an SGI machine?  If
>yes, please remove those definitions and rebuild your LDM distribution
>from scratch:
>
><as 'ldm'>
>cd ~ldm
>-- edit shell definition file and remove the environment variables that
>   were defined
>logoff
>login         (this is the easiest way to make sure the definitions are
>gone)
>
>cd ~ldm/ldm-6.3.0/src
>make distclean
>./configure
>make
>make install
>sudo make install_setuids
>
>If inappropriately defined environment variables is not causing your
>problem, please send us the contents of ~ldm/ldm-6.3.0/src/config.log
>and ~ldm/ldm-6.3.0/src/macros.make.
>
>Cheers,
>
>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.


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.