FYI, I solved the crashing exception... not sure why it matters but I
compiled it on a different host than before and it appears to working.
Once I have some test results I will post them to the list.

Thanks,

---
James T. Richardson, Jr.
[EMAIL PROTECTED]
eXcellence in IS Solutions, Inc.
713-862-9200 x226

Making IT Work for You
HPC & Enterprise IT Solutions
* HPC Application Acceleration
* Cluster Design, Deploy, Manage, Train
* Linux/Windows Integration
* Remote Management, Backup, Anti-Spam/Virus
* Network Assessments, Design
* Security Audits, Design
* Datacenter Design, Relocation
* Messaging and Collaboration


-----Original Message-----
From: Jeff Moyer [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 21, 2007 7:58 AM
To: Ian Kent
Cc: James Richardson; [email protected]
Subject: Re: [autofs] Slow mounts when using large round robin sets

Ian Kent <[EMAIL PROTECTED]> writes:

> On Thu, 2007-12-20 at 16:42 -0600, James Richardson wrote:
>> Jeff,
>> 
>> I downloaded the sources via git
>> (git://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git)
however
>> when automount starts up I get a floating point exception. I would
>> appreciate those debug patches you mentioned as I'm not sure where
the
>> floating point exception is occurring.
>
> I don't remember saying anything about debugging patches?

I mentioned that we could provide targeted debugging patches to
try to figure out the problem.  They do not exist yet, and they
certainly would not point out why he's getting a floating point
exception!  ;)

>> # strace automount -d
>> execve("/usr/sbin/automount", ["automount", "-d"], [/* 24 vars */]) =
0
>> uname({sys="Linux", node="c33n69", ...}) = 0
>> brk(0)                                  = 0x80041000
>> --- SIGFPE (Floating point exception) @ 0 (0) ---
>> +++ killed by SIGFPE +++
>> Process 3702 detached
>> [EMAIL PROTECTED] ~]# uname -a
>> Linux c33n69 2.6.21-GX #1 SMP Thu Apr 26 14:03:16 CDT 2007 i686 i686
>> i386 GNU/Linux
>
> I really don't know what's happening here.
> There's not enough info.

What Ian means is that you'd have to provide a stack trace from gdb at
the very least.  The output from automount -V wouldn't hurt, either.

-Jeff

NOTICE:
This message may contain privileged or otherwise confidential information.
If you are not the intended recipient, please immediately advise the sender
by reply email and delete the message and any attachments without using,
copying or disclosing the contents.



_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

Reply via email to