Search results

spiraling a bit off-topic: that sounds like a nice solution, i'm not sure it fits our use case though. i think our approach is not that uncommon: we have an ssd-equipped intermediate backup target that should keep, say, 4 backups per day, and daily backups for a week, as space permits. next...

any news on this? we also still get these errors. i created a local loop 'remote sync' as mentioned somewhere to provide a pre-pruned namespace for a slow downstream pbs instance (which accesses this pre-pruned namespace just fine). verify all works flawlessly on all bits and pieces, there...

We have 2 PBS instances, one with SSDs and the other with spinning rust. It's a bit tricky to get the timings right, so to visualize what is going on I wrote a small python script to convert the task logs of PBS into iCal ICS format. You can create one calendar per host and compare the times...

is there any SPICE on that dish yet? ;-)