NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Blair- Been there, done that! Obviously, you need to implement a cron job that tars or bzips up critical system files like that and maintain a rotating archive. We do a day of the week and monthly backups, which allows us to go back a year. These archives are rsynced to an offsite backup. We also use an inexpensive USB external drive to do period backups of critical stuff. Since I'm old, I usually print out a hardcopy of the pqact.conf and throw it in the file. Another critical cron task is to monitor disk space and alert you when it gets out of control. Depending on the editor you were using, it may have saved a backup copy of the file. With some editors, it will try to save a special copy if the editor crashes. Check your /tmp to see if any backup copy was written there. Good luck! Rodger Rodger R. Getz, President and CEO AWIS Weather Services 1735 East University Drive, Suite 101 Auburn, AL 36830-5204 Website: http://www.awis.com Facebook: https://www.facebook.com/AWISWeatherServices Phone: (334) 826-2149 ext 1004 Toll-free: (888) 798-9955 ext 1004 Toll-free Fax: (888) 374-8027 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or legally privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. On Jul 15, 2014, at 7:19 PM, Blair Trosper <blair.trosper@xxxxxxxxxxxxxxxxxxx> wrote: > I stupidly let our disk fill up, so when I tried to edit a config file, we > lost it. > > However, with LDM still running, it appears to be honoring it. Is there any > way (using ldmadmin -- or some other means) to get the LDM to cough out what > 'pqact.conf' file it's using so that I can restore it? > > I can try to re-build it by hand, but this could be a trial-and-error > process...hoping there's some way I can cheat to get the LDM to cough out > what it has in memory so I can copy/paste that back into the file. > > I'd like that to be back in place before I restart the LDM or apply any > patches the Debian server needs... > > (Imagine my embarrassment...) > > -- > > ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ > ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ > Blair Trosper > Updraft Networks / Weather Data > NOC: 844-UPDRAFT > Early Watch Notifications: http://twitter.com/weatherwatches > _______________________________________________ > ldm-users mailing list > ldm-users@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/
ldm-users archives: