similar to: [PATCH] support for wtmpdb (Y2038 safe wtmp replacement)

fup2p, this is offtopic for most lists Arnd Bergmann dixit: >It's hard because we don't even know what ioctls are affected at this point, >and I was hoping to get this part merged as a stepping stone in the process >of finding out. Oh okay. >e) ioctls that pass a time value as a 'long' or '__u32' instead of > 'time_t'. Fixing them requires

On Monday 18 May 2015 12:16:48 Thorsten Glaser wrote: > Arnd Bergmann dixit: > > >In the patch series I posted recently [1], I introduce new system calls to deal > >with modified data structures, but left the question open on how these should > >be best accessed from libc. The patches introduce a new __kernel_time64_t type > > Can we please have ioctls fixed for

Arnd Bergmann dixit: >In the patch series I posted recently [1], I introduce new system calls to deal >with modified data structures, but left the question open on how these should >be best accessed from libc. The patches introduce a new __kernel_time64_t type Can we please have ioctls fixed for mixed 32/64-bit systems such as MIPS (o32/n32/n64) and x86 (i386/x32/amd64) first, before

On 05/18/2015 02:53 AM, Arnd Bergmann wrote: > In the patch series I posted recently [1], I introduce new system calls to deal > with modified data structures, but left the question open on how these should > be best accessed from libc. The patches introduce a new __kernel_time64_t type > and based on that five new data structured: struct __kernel_timespec, > struct

In the patch series I posted recently [1], I introduce new system calls to deal with modified data structures, but left the question open on how these should be best accessed from libc. The patches introduce a new __kernel_time64_t type and based on that five new data structured: struct __kernel_timespec, struct __kernel_itimerspec, struct __kernel_stat, struct __kernel_rusage, and struct

I would have never imagined that I''d be bitten by the Y2038 bug someday... but it just happened and, trust me, it hurts! I have to deal with a database containing datetime fields with dates up to 2050 and more. ActiveRecord raises an exception because Ruby''s Time class implementation. Besides running Ruby on a 64-bit platform, what can be done to avoid that? Does a

Hello, Testing systems for Y2038 safety is done by setting the clock to after 2038, and then running all available test suites. This however requires that actual Y2038 issues are not masked by key expiry errors (when tests hardcode expiry dates), and this is what happens in this particular test. I've submitted a fix here: https://github.com/openssh/openssh-portable/pull/425 and here:

https://bugzilla.mindrot.org/show_bug.cgi?id=3684 Bug ID: 3684 Summary: regress/key-options.sh: update future key expiry date to far in the future Product: Portable OpenSSH Version: -current Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5

I'm pleased to announce the release of opusfile 0.12 The opusfile library provides seeking, decode, and playback of Opus streams in the Ogg container (.opus files) including over http(s) on posix and windows systems. opusfile depends on libopus and libogg. The included opusurl library for http(s) access depends on opusfile and openssl. Changes since the v0.11 release: - Fix stack overflow

xfs is the X Font Server, allowing remote X servers such as X Terminals to access fonts for rendering via legacy X11 core protocol requests. This release fixes a number of compiler warnings, and makes other code cleanups and changes to improve code maintainability and analyzer output. For those building for 32-bit platforms, it also enables use of the "large file" APIs - though no file

On Mon, 31 Jul 2023 09:25:12 +0800, "zhanghao1" <zhanghao1 at kylinos.cn> wrote: > A new virtio pci driver is added for listening to vcpus > inside guest. Each vcpu creates a corresponding thread to > periodically send data to qemu's back-end watchdog device. > If a vCPU is in the stall state, data cannot be sent to > back-end virtio device. As a result, the

Replace __time_t with time_t in my question. I've compiled function: std::string TimeValue::toString() const { // Alas, asctime is not re-entrant on Windows... //hb: __time64_t ourTime = this->toEpochTime(); time_t ourTime = this->toEpochTime(); //hb: char* buffer = ::asctime(::_localtime64(&ourTime)); char* buffer = ::asctime(::localtime(&ourTime)); std::string

Hi, I was thinking to ask the University computing Labs here to install R and I was told they need a statement that the software (R) is Y2K compliant. Which I cannot find in CRAN. (in addition to the licensing info). Is it a big issue to put such a statement in R? or this has legal implications that R do not want as a "free" software? If possible I would like to see the statement on

Release Announcements ===================== This is the first release candidate of Samba 4.20.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.20 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the first release candidate of Samba 4.20.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.20 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

hi, from reiserfs it`s known to happen quite often - wtmp may be corrupted; but actually I`m using only ext2/3 on the test machine. After 7 days running the RH8 system I`ve noticed the first corruption of wtmp. last shows only the line wtmp begins Wed Dec 11 09:14:52 2002 and /usr/sbin/dump-utmp wtmp spits out the history, e.g. the last line |Sun Dec 15 14:36:34 2002 ithum

It appears to be a pervasive assumption in the Portable OpenSSH code that wtmp and wtmpx records for the end of a session do not need to include the user name or hostname. Unfortunately Solaris appears not to go along with that assumption; the Solaris "last" command shows all login sessions initiated by OpenSSH as never terminating, or sometimes terminating with the user's next

Hello, after update my sshd to openssh-5.8_p2 (Linux Gentoo) I stated, that all ssh login (that open terminal session) causes writing of 2 records to a wtmp log. For example: user1 pts/4 gw.testdom.net Mon Jun 20 13:33 still logged in user1 ssh gw.testdom.net Mon Jun 20 13:33 - 13:38 (00:05) The first one is a standard record which appears only if a terminal

Hello! There is (still) problem with loging logins in wtmp (on Slackware 4 & Slackware 7). utmp & lastlog are successfully updated, but there is nothing in wtmp. Bye

Good day - I've checked where I can think to check, but I can find no mention of wtmp/utmp being supported in the standard Samba release at all. The closest I got was a posting from Joshua Lewis <jlewis@iosphere.net> dated Fri, 19 Jul 1996 08:06:55 -0400 (EDT) (almost exactly a year ago) which states in the final paragraph: > On another note, look for UTMP/WTMP support in Samba