This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Russ, > Steve, > > We are running LDM from our oper account, not the ldm account. Not > getting anywhere with kill -USR2 command from either account. The > ldmd.pid is stored in /home/ldm but is owned by oper. But the issue > seems to be syntax. > > [oper@fos2 ~]$ kill -USR2 'cat /home/ldm/ldmd.pid' > -bash: kill: cat /home/ldm/ldmd.pid: arguments must be process or job IDs The characters bracketing "cat /home/ldm/ldmd.pid" should be back-tics (`) rather than apostrophes ('). > [ldm@fos2 ~]$ kill -USR2 'cat /home/ldm/ldmd.pid' > -bash: kill: cat /home/ldm/ldmd.pid: arguments must be process or job IDs > > [ldm@fos2 ~]$ kill -USR2 'cat $HOME/ldmd.pid' > -bash: kill: cat $HOME/ldmd.pid: arguments must be process or job IDs > __________________________________________________________________________________________________ > [oper@fos2 ~]$ ls -l /home/ldm/ldmd.pid > -rw-r--r-- 1 oper ops 5 Aug 25 16:37 /home/ldm/ldmd.pid > > [oper@fos2 ~]$ ps -ef |grep ldm > oper 4840 1 0 Aug25 ? 00:00:00 rpc.ldmd -I 0.0.0.0 -P > 388 -M 256 -m 3600 -o 3600 -q /home/ldm/data/ldm.pq /home/ldm/etc/ldmd.conf > oper 5270 4809 0 18:48 pts/1 00:00:00 grep ldm > oper 6986 4840 1 Sep18 ? 01:54:46 rpc.ldmd -I 0.0.0.0 -P > 388 -M 256 -m 3600 -o 3600 -q /home/ldm/data/ldm.pq /home/ldm/etc/ldmd.conf > oper 6987 4840 1 Sep18 ? 02:03:23 rpc.ldmd -I 0.0.0.0 -P > 388 -M 256 -m 3600 -o 3600 -q /home/ldm/data/ldm.pq /home/ldm/etc/ldmd.conf Regards, Steve Emmerson Ticket Details =================== Ticket ID: VVJ-331218 Department: Support LDM Priority: Normal Status: Closed