linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problems using scsi_id with udevstart
Date: Wed, 06 Oct 2004 18:07:49 +0000	[thread overview]
Message-ID: <20041006180749.GA10986@vrfy.org> (raw)
In-Reply-To: <1097019226.2300.38.camel@bluto.andrew>

On Wed, Oct 06, 2004 at 11:33:55AM -0600, Andrew Patterson wrote:
> On Wed, 2004-10-06 at 18:44 +0200, Kay Sievers wrote:
> > 
> > Where is the "path = /sbin/scsi_id" line coming from? Other lines are missing.
> > Did you change anything in the code. It should look more like this:
> > 
> 
> Yep, added some debugging code.  Here are the diff's:

Ok, I've no idea :) Could you please try:

  DEVPATH=/block/sda ACTION­d strace -o /tmp/udev-callout-trace -f -s1000 /sbin/udev block

It will create a ~2MB file in /tmp with something like this:

  26863 rt_sigaction(SIGPIPE, {0x2ab9a0, [], SA_RESTORER, 0x212718}, {SIG_DFL}, 8) = 0¶
  26863 send(3, "<15>Oct  6 19:52:27 udev: execute_program: execute \'/sbin/scsi_id\' with main argument", 85, 0) = 85¶
  26863 rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0¶
  26863 execve("/sbin/scsi_id", ["/sbin/udev", "block"], [/* 26 vars */]) = 0¶
  26863 uname({sys="Linux", node="pim", ...}) = 0¶
  26863 brk(0)                            = 0x9f0e000¶
  ...

This should give us some more information.
Please send it to me by privat email.

Thanks,
Kay


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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

  parent reply	other threads:[~2004-10-06 18:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 23:33 Problems using scsi_id with udevstart Andrew Patterson
2004-10-05 23:53 ` Patrick Mansfield
2004-10-05 23:55 ` Kay Sievers
2004-10-06 16:20 ` Andrew Patterson
2004-10-06 16:26 ` Andrew Patterson
2004-10-06 16:44 ` Kay Sievers
2004-10-06 16:59 ` Patrick Mansfield
2004-10-06 17:33 ` Andrew Patterson
2004-10-06 18:07 ` Kay Sievers [this message]
2004-10-06 18:42 ` Andrew Patterson
2004-10-06 19:13 ` Kay Sievers
2004-10-06 21:22 ` Andrew Patterson
2004-10-06 21:39 ` Kay Sievers
2004-10-06 22:24 ` Greg KH
2004-10-06 22:28 ` Andrew Patterson
2004-10-06 23:08 ` Kay Sievers
2004-10-06 23:19 ` 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=20041006180749.GA10986@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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).