From miek at miek.nl Mon Apr 16 09:29:08 2012 From: miek at miek.nl (Miek Gieben) Date: Mon, 16 Apr 2012 11:29:08 +0200 Subject: [dsc] 4 hour timescale presenter bug Message-ID: <20120416092908.GB4437@miek.nl> Hello, We are encountering an old bug in the dsc presenter, where the 4 hour images contain gaps. http://www.measurement-factory.com/pipermail/dsc/2010-November/000274.html I've packaged dsc for ubuntu, by using the debian/ directories from debian, this works wonderful. This also means we are using ploticus 2.41. The suggested fix: "downgrade to ploticus 2.40" is *not* something I want to do... Is there any other way to fix this? Regards, -- Miek Gieben From tcameron at dyn.com Thu Apr 26 18:04:24 2012 From: tcameron at dyn.com (Tom Cameron) Date: Thu, 26 Apr 2012 14:04:24 -0400 (EDT) Subject: [dsc] Patch for upload-rsync.sh.diff In-Reply-To: <726265066.12143053.1335463198994.JavaMail.root@zmail-01.mht.dyndns.com> Message-ID: <1083963613.12144489.1335463464188.JavaMail.root@zmail-01.mht.dyndns.com> My organization uses DSC, but we're running into a problem where the previous run of the script is ending during inconvenient times during the current script's execution. For instance, the PID file will exist when the script performs "if test -f $PIDF; then", but it does not exist when the script tries to "PID=`cat $PIDF 2> /dev/null`". Other times, we successfully retrieve the PID from the PID file, but by the time the script attempts to "kill -0" the PID, the process has already completed. Attached is a very simple patch that simply pipes STDERR from these statements to /dev/null so CRON doesn't report an error. Please feel free to provide feedback. Thanks! Tom -- Tom Cameron System Engineer Dyn, Inc. Pho. 603-668-4998 Mob. 603-289-0124