Sponsored Content
Full Discussion: Solaris 64bit and Y2038 bug
Operating Systems Solaris Solaris 64bit and Y2038 bug Post 302452438 by nullpt on Friday 10th of September 2010 11:19:42 AM
Old 09-10-2010
Solaris 64bit and Y2038 bug

Hi all,

I'm runing a 64bit Solaris 9 system that supposedly isn't affected by the y2038 bug. If so, why can't I set de that from that point in time forward?

Code:
root@machine>uname -a
SunOS machine 5.9 Generic_118558-36 sun4u sparc SUNW,Sun-Fire-V440
root@machine>isainfo -b
64
root@machine>mktime -y +27
2037-09-10 16:18:18
root@machine>mktime -y +28
mktime: invalid time

Thanks in advance
BR
AJ

Last edited by Scott; 09-10-2010 at 01:21 PM.. Reason: Please use code tags
 

8 More Discussions You Might Find Interesting

1. Solaris

fsck bug in Solaris 8

Be careful, we've just found out that the fsck command in Solaris 8 has caused corruption of our ufs files-stores. This was introduced in patch SUNWcsu patch 110910-05. Be warned, Sun are fixing this as we speak :eek: (1 Reply)
Discussion started by: Maillot Jaune
1 Replies

2. Solaris

CC 5.5 compiler flag to issue 64bit porting warnings on sparc-solaris

Hi, We are porting our application from 32bit to 64bit. We tried -xarch=v9, -xarc=v9a and -xport64=full options so that compiler to issue 64bit porting warnings. But we are not getting any porting warninings WE are using CC 5.5 compiler on sparc-solaris m/c. Please tell us some powerful... (0 Replies)
Discussion started by: shobhah
0 Replies

3. Solaris

32bit / 64bit issue with x86 solaris

i have solaris 10 x86 64bit installed on my pc (dell 3100). i then decided to move my hard drive to another pc (dell 4600). I noticed that each time i boot up, the OS show as 32 bit (instead of 64bit) and i can't even get past this stage to the login page. when i moved it back to dell 3100 it... (13 Replies)
Discussion started by: seyiisq
13 Replies

4. Solaris

Solaris SPARC 10 64Bit -JDK Installation 1.6.05

In Sun Solaris 10, not able to create the key. JDK 1.6 Installed & PATH & JAVA_HOME both are referred to jdk 1.6. It is showing the belwo error Error: wrap() failed java.security.InvalidKeyException: wrap() failed at sun.security.pkcs11.P11RSACipher.engineWrap(P11RSACipher.java:395) at... (10 Replies)
Discussion started by: saktiviji
10 Replies

5. Solaris

Apcahe2 64bit on solaris 10 sparc!

Hi, i'm trying to compile apache 2.2.13 on solaris 10 sparc as 64bit and for some reason its always compiled as 32bit! i know it can be done cause i've already done it before, so i'm not sure what am i doint wronghttp://forums.digitalpoint.com/images/smilies/frown.gif i've edit /.profile... (0 Replies)
Discussion started by: levic
0 Replies

6. Solaris

Where to download solaris 10 for sparc 64bit?

hi all I just got a sun blade 2000 server for free. I need to load a solaris 10 for sparc OS to it. the memory inside the box is 5gb. the cup is SUNW,UltraSPARC-III+ (1200 MHz @ 8:1, 8 MB). so my questions is 1. do I need to install a 64bit os or a 32bit os? 2. where can I download the... (3 Replies)
Discussion started by: rs6000er
3 Replies

7. Solaris

where can i download solaris 10 64bit for my intel machine?

where can i download solaris 10 64bit for my intel machine? i am able to find only 32bit solaris for intel machine. Please help me.. (2 Replies)
Discussion started by: chidori
2 Replies

8. Solaris

SUNWi1cs SUNWi15cs packages for solaris 10 64bit sparc

hi, i need to install SUNWi1cs and SUNWi15cs packages for solaris 10 sparc 64 bit , where can i download these packages . Thanks . (2 Replies)
Discussion started by: zeeshan047
2 Replies
SYSTEMD-MACHINE-ID-SETUP(1)				     systemd-machine-id-setup				       SYSTEMD-MACHINE-ID-SETUP(1)

NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id SYNOPSIS
systemd-machine-id-setup DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with a provisioned or randomly generated ID. See machine-id(5) for more information about this file. If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty. The new machine ID will be acquired in the following fashion: 1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID in /etc/machine-id. 2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID. The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM. 3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the machine ID. For details, see the documentation of the Container Interface[1]. 4. Otherwise, a new ID is randomly generated. The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below. Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images. OPTIONS
The following options are understood: --root=root Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for /etc/machine-id itself. --commit Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point. This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure that this file is always valid and accessible for other processes. This command is primarily used by the systemd-machine-id-commit.service(8) early boot service. --print Print the machine ID generated or committed after the operation is complete. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1) NOTES
1. Container Interface https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)
All times are GMT -4. The time now is 03:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy