Starting with an empty wtmpx. I ssh to the machine. I then do last and get pas pts/6 Thu Jan 1 01:00 still logged in Using fwtmp to convert the wtmp file to asci I get pas ts/6 pts/6 1886 7 0000 0000 0 1042034068 0 0 Thu Jan 1 01:00:00 1970 If I log in using ssh or on the console then these do not appear in last.
This is apparently a bug with compiling in 64 bit. David foster saw this. http://www.sunmanagers.org/pipermail/summaries/2002-October/004018.html
Checked against latest snapshot.Problem is still there.
I really want to know why people are compiling software in 64bit when there is zero logical reason. Nor any physical gain. A lot of 64bit platforms have issues with their [uw]tmp[.] files while crossing from 32bit to 64bit due to alignments and such. However, no one has bother to give me a good reason why the code should be #ifdef/#endif to hell to support a behavior.
It is simple laziness. We have applications that require 64 bit. We therefor have to have to libraries compiled in 64 bit. Rather than build two copies of all the libraries we build everything in 64 bit.
I see the same problem on IA64 HP/UX 11.22. Is there any workaround when openssl need to be 64 bit?
Created attachment 471 [details] Use updwtmpx for 64bit platforms that support it (no configure.ac) add a "#define HAVE_UPDWTMPX 1" into your config.h and apply this patch. Does this solve your problem?
The patch solved the problem on HP/UX 11.22 for me. :)
Comment on attachment 471 [details] Use updwtmpx for 64bit platforms that support it (no configure.ac) Tests OK (with the appropriate addition to configure) on Solaris 8 (32 bit), HP-UX 11.00 (32&64 bit). AIX doesn't have updwtmpx.
I can confirm this does work under Solaris 9. As long as it it detected I'm ok with it.
Patch applied, thanks.
Mass change of RESOLVED bugs to CLOSED