Re: [Pkg-zfsonlinux-devel] Bug#595790: hostid: useless unless fixed

2016-09-29 Thread Michael Stone
On Wed, Sep 28, 2016 at 09:03:38PM -0700, Richard Laager wrote: Getting back to ZFS and /etc/hostid... I would think that a randomly-generated /etc/hostid is probably sufficient. Whether that's done in the libc, spl, or zfs package makes no difference to me. You still haven't explained why zfs

Re: Bug#595790: [Pkg-zfsonlinux-devel] Bug#595790: hostid: useless unless fixed

2016-09-28 Thread Michael Stone
On Thu, Sep 29, 2016 at 12:30:39AM +0200, Aurelien Jarno wrote: Another question is about chroots. The above methods means we might end-up with the same machine-id in chroots id the DMI UUID is available. Is it something really wanted? One of the many ambiguities of gethostid. :) Is it a unique

Re: [Pkg-zfsonlinux-devel] Bug#595790: hostid: useless unless fixed

2016-09-28 Thread Michael Stone
On Wed, Sep 28, 2016 at 11:11:21PM +0200, Petter Reinholdtsen wrote: [Michael Stone] Other platforms have deprecated gethostid, that's the best way forward for linux, IMO. Which platforms is this? I find FreeBSD recommend to use sysctl and KERN_HOSTID to get the hostid integer directly

Re: [Pkg-zfsonlinux-devel] Bug#595790: hostid: useless unless fixed

2016-09-28 Thread Michael Stone
On Wed, Sep 28, 2016 at 12:32:04PM +0200, Florian Weimer wrote: * Petter Reinholdtsen: Something like this should work, I guess: if [ ! -f /etc/hostid ]; then if [ -e /sys/class/dmi/id/product_uuid ]; then sethostidfromuuid $(cat /sys/class/dmi/id/product_uuid) else dd if=/

Re: Bug#595790: hostid: useless unless fixed

2013-02-20 Thread Michael Stone
On Thu, Feb 21, 2013 at 01:08:00AM +0100, Carlos Alberto Lopez Perez wrote: When you create a ZFS pool the value of the hostid is stored inside it. When the system is going to import a pool it checks if the hostid stored inside the pool matches the current host hostid. If it don't matches it refu

Re: FW: Bug#641832: bizarre behavior of timer_settime on kfbsd

2011-09-19 Thread Michael Stone
On Fri, Sep 16, 2011 at 10:20:10PM +0200, Petr Salinger wrote: "true" sometimes exits too fast, "sleep 0.1" suffices. Due to userspace implementation (via pthread_cond_timedwait), /bin/true might end even before the signal is delivered. BTW, I just verified, only kfreebsd-i386 is affected, kfree

Re: FW: Bug#641832: bizarre behavior of timer_settime on kfbsd

2011-09-16 Thread Michael Stone
On Fri, Sep 16, 2011 at 09:11:28PM +0200, Petr Salinger wrote: fail on subsequent runs. Much smaller (order of magnitude) numbers seem ok, and I haven't identified a specific bad number. In a loop, 8 seems ok, while 9 exhibits intermittant failure. Assuming that holds true, we cou

Re: FW: Bug#641832: bizarre behavior of timer_settime on kfbsd

2011-09-16 Thread Michael Stone
On Fri, Sep 16, 2011 at 07:24:41PM +0200, Petr Salinger wrote: If any debian-bsd people could add some insight to this one, it would be appreciated. I've tried various test values, and it doesn't require the time be exactly MAX_INT to fail (smaller values fail also). Please which one ? The 4

FW: Bug#641832: bizarre behavior of setitimer on kfbsd

2011-09-16 Thread Michael Stone
If any debian-bsd people could add some insight to this one, it would be appreciated. mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $? 0 mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $? 0 mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; ech