From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udevd test script
Date: Fri, 16 Apr 2004 23:04:42 +0000 [thread overview]
Message-ID: <20040416230442.GB22314@kroah.com> (raw)
In-Reply-To: <20040415201141.GA11625@vrfy.org>
On Thu, Apr 15, 2004 at 10:11:41PM +0200, Kay Sievers wrote:
> Thanks to Yin, Hu <hu.yin@intel.com>, who made a nice perl script to
> test the expected behavior of the udevd sequence number handling. The
> test sends different SEQNUM sequences to udevd, while analyzing the
> reordering and timeout handling of udevd.
Hm, I've applied this but can't run it :(
I keep getting the error:
Opening file /tmp/udev_log.txt: No such file or directory at ./udevd-test.pl line 148.
It looks like the log file is deleted and then it is attempted to be
opened, but this fails as it isn't there anymore...
Care to fix this?
Oh, and if you run the latest udev_test.pl, we have a bunch more tests,
including a few that fail, if you were looking for something to do :)
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-04-16 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 20:11 [PATCH] udevd test script Kay Sievers
2004-04-16 23:04 ` Greg KH [this message]
2004-04-17 0:04 ` Kay Sievers
2004-04-17 0:16 ` Greg KH
2004-04-17 0:21 ` Kay Sievers
2004-04-17 0:35 ` Greg KH
2004-04-17 1:30 ` Kay Sievers
2004-04-17 1:33 ` Kay Sievers
2004-04-17 2:21 ` Nick Yin
2004-04-21 16:50 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040416230442.GB22314@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).