[rescue] looking for IBM System/36 software
sun.mail.list47 at oryx.us
Sun Mar 29 00:53:14 CDT 2015
Sadly, I don't have any Omni OS experience because I can't get past the chip on
my shoulder of the OS running off of a USB stick vs the HDD. That said, they
are doing some awesome stuff.
Assuming they haven't deviated too far off course, the timezone for either the
global or local zone(s) should be set in the /etc/default/init file.
The relevant line should look like this:
reflecting your location.
I'm guessing that you probably already knew this stuff anyway. Maybe you are
stating that you have all this stuff correct, and the VM still has it (4) hours off?
There is also some more detailed time zone stuff specific to dealing with issues
on x86 hardware on the Solaris X86 FAQ under section 6.12 here:
I had to use the "rtc" command on some x86 systems, but that was a long time ago.
Because $WORK has me working on Solaris boxes at various data centers in various
time zones, I keep this alias in my .cshrc file to remind me what time zone the
server I am working on is in.
goldfish /home/jkemp 403 % date
Sunday 29 March 2015 00:38 CDT
goldfish /home/jkemp 404 % grep date .cshrc
alias date '/bin/date +"%A %d %B %Y %H:%M %Z"'
goldfish /home/jkemp 405 %
This is examples from my personal equipment at $HOME. To do otherwise would be
a career limiting move.
All food for thought, hope something in here helps,
On 03/29/15 12:08 AM, Cory Smelosky wrote:
> On Sun, 29 Mar 2015, Jerry Kemp wrote:
>> 4 hours. Wow.
>> I think your mail server is fluctuating between east coast and west coast
>> time. :)
> ... that is genuinely possible. I have 0 CLUE what the timezone the client VM is
> really in...
> cory at meaghan :~ uname -a
> SunOS meaghan 5.11 omnios-10b9c79 i86pc i386 i86pc
> I think I'm going to head back to FreeBSD for this so I can do latd.
More information about the rescue