search for: biocontroller

I was up late last night trying to find the cause of this, but I''m stumped. I have this relatively simple controller to load up a bio. It''s basicly id, name, desc, type (I use STI). class BioController < ApplicationController layout ''layouts/singlepanel'' def index @bio = Bio.find(:all, :conditions => [''site_id = ?'', @session[''site''].id]) render ''bio/index'' end end However when I attempt to dis...

Hi all, With this series of patches, you can determine the owners of any type of I/Os. I ported the previous version to linux-2.6.26-rc2-mm1. This makes dm-ioband -- I/O bandwidth controller -- be able to control the Block I/O bandwidths even when it accepts delayed write requests. Dm-ioband can find the owner cgroup of each request. It is also possible that OpenVz team and NEC Uchida-san team

Hi all, With this series of patches, you can determine the owners of any type of I/Os. I ported the previous version to linux-2.6.26-rc2-mm1. This makes dm-ioband -- I/O bandwidth controller -- be able to control the Block I/O bandwidths even when it accepts delayed write requests. Dm-ioband can find the owner cgroup of each request. It is also possible that OpenVz team and NEC Uchida-san team

Hi All, I''m using shorewall 4.0.15-1 on debian 5.0.5 and It works fine. I want to start using rules based on users. This is supported in the shorewall-rules file, However it seems that each rule can only be associated with one user or group. Does this mean that I cannot have a rule apply to several users which belong to several groups? Will creating duplicate rules for each user

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Are you using wins? Try lmhosts for the start? Are all machines on the same subnet? Just a few hints to start with ... Christian > > > I have absolutely no clue what I could do to fix it. The only solution I > can think of, is to downgrade to redhat 6.2. > > Your help would be greatly appreciated. > > Stefan Kaes > > portax.com GmbH > Zielstattstrasse 40, Geb.

Are you using wins? Try lmhosts for the start? Are all machines on the same subnet? Just a few hints to start with ... Christian > > > I have absolutely no clue what I could do to fix it. The only solution I > can think of, is to downgrade to redhat 6.2. > > Your help would be greatly appreciated. > > Stefan Kaes > > portax.com GmbH > Zielstattstrasse 40,

\\Pettit Connect As: Password: On the server side, I didn't get far because the domain name come up NULL so it failed on that test. Below are two logs log98.txt and log2000.txt that show full debug info. I might just have a stupid configuration or installation mistakes. I am sure that my basic configuration must work since it is a very typical setup. Any help will be highly appreciated

copy d:\bugs.ps \\ouessant\lexmark after having deleted all the samba log files and restarted the SMBd daemon from the SWAT Web interface. This leads to the INTERNAL ERROR, see samba.oulx Now, to locate the problem, I tried the same kind of command on the same file, bugs.ps, but using the SMBCLIENT application from the Linux server itself, without changing anything, nor restarting the SMBd