search for: sloution

I want to revert back to a previous version of rails (1.2.3) but the project I want to work on was created in 2.0.2. I have uninstalled 2.0.2 and gem installed 1.2.3 but when I run script\server I get the following error. (I''m guessing its to do with my environment file but I''m pretty new to Rails so Im not sure.)

Hi, I have been asked to produce a binary of some software for somone running R on Mac OS X. I don't have a Mac and don't know anything about them. The sloution would seem to be to obtain/build a crsoo compiler on windows or probably easier on Linux i686. I would appreciate any advice on how how to go about this. I understand there are a number of different versions of Mac OS X. Are there compatability issues? also 32/64 bit issues. Dave -- Dav...

In case a system is incapable of fax relay or if it is disabled, one of the easiest and safest options is to go for 40 kbps ADPCM compression (for fax upto 14.4 kbps)..even am new to this problem and the fair bit of seraching which i've done seems to suggest that the standard sloutions are to simply 'bypass' it else compress using ADPCM (40 k for fax upto 14.4 k, 32 k for fax upto 9.6 k and so on), both of which eat up a lot of bandwidth. So, speex sounds great! Once I start playing with the non-speech traffic will keep u posted. Cheers, Mainak On 5/7/07, Jean-Marc Vali...

...oy them > instead? > I think this happens when a device is removed. > > Thoughts? > Agree, vhost net removal should not be blocked by a skb. But since the skbs could be queued may places, just destroy them may need extra locks. Haven't thought this deeply, but another possible sloution is to rcuify destructor_arg and assign it to NULL during vhost_net removing. >> --- >> drivers/vhost/net.c | 17 +++++++---------- >> 1 file changed, 7 insertions(+), 10 deletions(-) >> >> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c >> index a0fa5d...

...oy them > instead? > I think this happens when a device is removed. > > Thoughts? > Agree, vhost net removal should not be blocked by a skb. But since the skbs could be queued may places, just destroy them may need extra locks. Haven't thought this deeply, but another possible sloution is to rcuify destructor_arg and assign it to NULL during vhost_net removing. >> --- >> drivers/vhost/net.c | 17 +++++++---------- >> 1 file changed, 7 insertions(+), 10 deletions(-) >> >> diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c >> index a0fa5d...

...emoved. >>> >>> Thoughts? >>> >> >> Agree, vhost net removal should not be blocked by a skb. But since the >> skbs could be queued may places, just destroy them may need extra locks. >> >> Haven't thought this deeply, but another possible sloution is to rcuify >> destructor_arg and assign it to NULL during vhost_net removing. > > Xen treat it by a timer, for those skbs which has been delivered for a > while, netback would exchange page of zero_copy's skb with dom0's page. > > but there is still a race between hos...

...emoved. >>> >>> Thoughts? >>> >> >> Agree, vhost net removal should not be blocked by a skb. But since the >> skbs could be queued may places, just destroy them may need extra locks. >> >> Haven't thought this deeply, but another possible sloution is to rcuify >> destructor_arg and assign it to NULL during vhost_net removing. > > Xen treat it by a timer, for those skbs which has been delivered for a > while, netback would exchange page of zero_copy's skb with dom0's page. > > but there is still a race between hos...

When I try to run script/breakpointer, I get the following error: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `getaddrinfo'': getnameinfo: Non-recoverable failure in name resolution (SocketError) It''s Rails 1.0 on OSX 10.4.4. Any suggestions?

...id not want that too much, Gothic 3 - with russian patches from Mighty Dwarf or so, runs very fast according to slow at AppDB), KotOR I and II, etc... I'm stuck at Mass Effect. There is no idea what else I can do - I've tried everything except sleeping for 3+ month without trying to find a sloution. Mass Effect installs, runs, I can create character and then on first sequence intro video where there should be a dialog I can only see the Earth on the screen and game freezes. With wine 1.5 I doubled that by getting the loading screen grayscale (switching to 1.4 makes it coloured back). Byt the...

...t; >>Agree, vhost net removal should not be blocked by a skb. But since the >>>> > >>skbs could be queued may places, just destroy them may need extra locks. >>>> > >> >>>> > >>Haven't thought this deeply, but another possible sloution is to rcuify >>>> > >>destructor_arg and assign it to NULL during vhost_net removing. >>> > > >>> > >Xen treat it by a timer, for those skbs which has been delivered for a >>> > >while, netback would exchange page of zero_copy's...

...t; >>Agree, vhost net removal should not be blocked by a skb. But since the >>>> > >>skbs could be queued may places, just destroy them may need extra locks. >>>> > >> >>>> > >>Haven't thought this deeply, but another possible sloution is to rcuify >>>> > >>destructor_arg and assign it to NULL during vhost_net removing. >>> > > >>> > >Xen treat it by a timer, for those skbs which has been delivered for a >>> > >while, netback would exchange page of zero_copy's...

Hi all, I'm currently trying to run multiple Diablo 2 Windows with 1 user. Thats what i managed to do until now: if I use export WINEPREFIX=~/.wine2 and then run a copied d2, it works to join bnet twice, but when both are in the same game, 1 will get a Timeout. So i tried to find a sloution (and found one): I made another user (called "d21") and installed D2 into his personal .wine folder. Now when I can have both accounts in the same game without getting a timeout, but i have to switch between the users all the time. So i thought i could start a console with my first accou...

Problem: -------- On the client mascines I get the msg: "The account is not authorized to log in from this station." This has bugged me for days now, so I am posting this sloution around varius places on the net... Analysis: --------- from a round of analysis by Jamz Boman B.Sc (Jamz@Boman.com), Toby Corkindale (tjcorkin@steadycom.com.au) Andreja Zivkovic (zivkotech@ozemail.com.au) at http://www.linuxsa.org.au/mailing-list/1999-02/474.html Jamz Boman wrote: > > How...

...gt;>Thoughts? > >>> > >> > >>Agree, vhost net removal should not be blocked by a skb. But since the > >>skbs could be queued may places, just destroy them may need extra locks. > >> > >>Haven't thought this deeply, but another possible sloution is to rcuify > >>destructor_arg and assign it to NULL during vhost_net removing. > > > >Xen treat it by a timer, for those skbs which has been delivered for a > >while, netback would exchange page of zero_copy's skb with dom0's page. > > > >but there i...

...this happens when a device is removed. >> >> Thoughts? >> > > Agree, vhost net removal should not be blocked by a skb. But since the > skbs could be queued may places, just destroy them may need extra locks. > > Haven't thought this deeply, but another possible sloution is to rcuify > destructor_arg and assign it to NULL during vhost_net removing. Xen treat it by a timer, for those skbs which has been delivered for a while, netback would exchange page of zero_copy's skb with dom0's page. but there is still a race between host's another process han...

Hi Jean, Thats great news for me to start off with as I was planning to go with 16 Kbps ADPCM keeping in mind the issues and options I had. Now, whether the additional computation cost is worth the significant bandwidth savings, I have to see. Just wondering if it is possible to extend this logic to G3 and G4 fax as well, i.e. using a higher bit-rate and complexity mode for modem or fax instead of

We used to stop the handling of tx when the number of pending DMAs exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation of both host and guest. But it was too aggressive in some cases, since any delay or blocking of a single packet may delay or block the guest transmission. Consider the following setup: +-----+ +-----+ | VM1 | | VM2 | +--+--+

We used to stop the handling of tx when the number of pending DMAs exceeds VHOST_MAX_PEND. This is used to reduce the memory occupation of both host and guest. But it was too aggressive in some cases, since any delay or blocking of a single packet may delay or block the guest transmission. Consider the following setup: +-----+ +-----+ | VM1 | | VM2 | +--+--+