csa
[Top] [All Lists]

Re: Two Simple Questions

To: Andrew Fant <andrew.fant@xxxxxxxxx>
Subject: Re: Two Simple Questions
From: Jay Lan <jlan@xxxxxxx>
Date: Fri, 15 Oct 2004 14:08:38 -0700
Cc: Robin Holt <holt@xxxxxxx>, csa@xxxxxxxxxxx
In-reply-to: <123050000.1097873483@xxxxxxxxxxxxxxxxxx>
References: <31770000.1097851964@xxxxxxxxxxxxxxxxxx> <20041015152049.GC873@xxxxxxxxxxxxxxxxxxxxxxxxx> <41700B10.1070102@xxxxxxx> <20041015173837.GG873@xxxxxxxxxxxxxxxxxxxxxxxxx> <20041015174254.GH873@xxxxxxxxxxxxxxxxxxxxxxxxx> <111360000.1097871666@xxxxxxxxxxxxxxxxxx> <41703754.2040409@xxxxxxx> <123050000.1097873483@xxxxxxxxxxxxxxxxxx>
Sender: csa-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Yes, you were right. But then 'rmmod csa' cleans it up. Just
a workaround until the real fix is released.

I will try to release the fixes later next week. It needs fixes
to both the rpm and kernel patch.

- jay


Andrew Fant wrote:


--On Friday, October 15, 2004 13:47:16 -0700 Jay Lan <jlan@xxxxxxx> wrote:


Sorry about the csa_halt bug. It has been identified and fixed.
We know that bug had nothing to do with the ja problem you mentioned.

To get around the csa_halt problem, please just recycle the csa
by doing "/etc/init.d/csa stop; /etc/init.d/csa start".

Thanks,
  - jay



Jay,
Thanks for the information, but /etc/init.d/csa stop calls /usr/sbin/csaswitch -c halt, so that won't actually stop it, as far as I can tell.

Andy


<Prev in Thread] Current Thread [Next in Thread>