* Jeremy Thornhill jeremy.thornh...@gmail.com [2010-12-20 20:02]:
On Sun, Dec 19, 2010 at 10:27 AM, Jeremy Thornhill
jeremy.thornh...@gmail.com wrote:
FWIW I've created an issue for this http://www.illumos.org/issues/537
and if I find any useful info I'll post it there.
To reply to
On Mon, Dec 20, 2010 at 3:17 PM, Guido Berhoerster g...@openindiana.org wrote:
Thanks for investigating this, time-slider is still developed in
the open by Oracle, see
http://src.opensolaris.org/source/xref/jds/time-slider/
We currently ship the latest version so this has not been fixed
* Jeremy Thornhill jeremy.thornh...@gmail.com [2010-12-20 22:21]:
I have created an issue in the Opensolaris bug tracker and I've
updated the Illumos ticket with the URL. Hopefully they will fix it,
if not I'd be glad to hack together a patch that makes this not happen
in OI. I'm no python
On Sat, Dec 18, 2010 at 11:56 PM, Albert Lee tr...@opensolaris.org wrote:
Can you check crontab -e as root and ensure nothing related to
auto-snapshot is still present?
Albert,
I double checked, and nothing is in there. I had already disabled this one:
#5,20,35,50 * * * *
On Fri, Dec 17, 2010 at 1:35 PM, Jeremy Thornhill
jeremy.thornh...@gmail.com wrote:
Hello list,
I've encountered a bizarre situation with time-slider on OI 147. As
background, this is a x86 system that's been upgraded from OpenSolaris
snv_133, and the time-slider configuration I'm using is
Hello list,
I've encountered a bizarre situation with time-slider on OI 147. As
background, this is a x86 system that's been upgraded from OpenSolaris
snv_133, and the time-slider configuration I'm using is unmodified
post-upgrade (save for disabling the legacy time-slider-cleanup cron
job).
