similar to: Inbox re-initialized

Displaying 20 results from an estimated 140 matches similar to: "Inbox re-initialized"

2007 Aug 29
3
too many files opened
Hi folks, My institute's mail server was upgraded to RHEL5 with dovecot 1.0-2.1rc5 recently. And it uses PAM authentication which points to LDAP server. Now from time to time it gets Error like dovecot: Aug 29 09:23:59 Error: auth(default): pam(joshua,192.168.177.52): pipe() failed: Too many open files and users can not login. My config is like dovecot -n # /etc/dovecot.conf base_dir:
2006 Oct 29
0
windows nt4, 2k cannot join samba domain
Hello folks, I am having some problem setting up the following. I was rebuild my friend's old windows nt domain. The old Windows NT4 server will be replaced by a Samba PDC, all windows 2k client will rejoin the samba domain. Now the samba server is setup, windows 2k joins it and I can see the 'welcome to xxx domain' message and reboot the windows 2k client. At the next login, it gave
2004 May 09
0
''initialized'' extension script renamed
Yesterday, I announced the addition of an ''initialized'' extension script that can be used to run commands contained in the ''common'' script under Shorewall 1.x but that have nothing to do with the ''common'' chain. I''ve decided to call the new script ''initdone'' rather than ''initialized'' because I
2008 Nov 05
1
Constants in models are initialized before fixtures are loaded?
Hi, here''s simplified code from the model: class Foo < AR::Base FIRST = Foo.first.id end The problem is that when testing I get well known error: "Called id for nil...". I guess that this constant is initialized before the fixtures are loaded. Is there any way to fix it? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are
2012 May 29
0
racc/parser.rb:27: warning: already initialized constant Racc_Runtime_Version
Hi, I tried this puppet shell command and I''m getting a warning: oracle@z3:/pt/b/puppet$ puppet describe -s user racc/parser.rb:27: warning: already initialized constant Racc_Runtime_Version Here is some info about my setup: oracle@z3:/pt/b/puppet$ oracle@z3:/pt/b/puppet$ ruby -v ruby 1.9.2p318 (2012-02-14 revision 34678) [x86_64-linux] oracle@z3:/pt/b/puppet$ oracle@z3:/pt/b/puppet$
2009 Jan 29
0
How to get rid of an ActiveRecord warning "already initialized constant"
I need to get a proxy class for a specific AR validation I reuse a piece of code (from Globalize), where it''s set as a constant : module Globalize module Model module ActiveRecord class << self def create_proxy_class(klass) Object.const_set "#{klass.name}Translation", Class.new (::ActiveRecord::Base){..} .. end so in my validation module,
2005 Sep 14
0
RE: [PATCH][VT] Clear the pending interrupt on sharedpage when PIC initialized
Keir Fraser wrote: > On 13 Sep 2005, at 03:40, Jiang, Yunhong wrote: > >> 1) I think the cpu_reset_interrupt() is a common API on qemu for >> hardware interrupt/exception etc,while clear the shared page is just >> for hardware interrupt. Of course, this function is currently used >> just for hardware interrupt since qemu works as a device model :) >> But
2009 Oct 02
0
warning: already initialized constant ...
Hi, Every time I start the console, run tests or start any rake thing I get this at the beginning: /home/sweethome/railsproject/vendor/rails/railties/lib/rails/ version.rb:3: warning: already initialized constant MAJOR /home/sweethome/railsproject/vendor/rails/railties/lib/rails/ version.rb:4: warning: already initialized constant MINOR
2008 Nov 06
0
Restore password without session initialized
Hi, Y was triying to implement in my application the fact of remenber or generate a new password. When you try to loggin in there, if the password is no correct, the application shows the link "Remenber password", having the route /users/remind. The problem is when a try to go to this link, appear an error like this: undefined local variable or method `new_session_path'' for
2005 Apr 01
1
warning: already initialized constant (is this a bug?)
since I upgraded to 0.11.1 I get a string of "warning: already initialized constant" errors in my error log. I couldn''t figure it out. I created a blank rails project to test it. two models : account belongs_to :user user has_many :accounts in the accounts model, I set the following constants CLOSED = 0 INACTIVE = 1 ACTIVE = 2 then I set up a test controller with a simple
2001 Nov 08
0
sessionid.tdb not initialized
I did do a install from the cvs and i restarted my smbd and nmbd. when typing ./smbstatus it gives me sessionid.tdb not initialized. What causes this and what do i have to do to fix it? thanks in advance Matt
2009 Aug 17
1
[menu] Bug: 'cm' is used before it is initialized
Hi, I'm seeing a problem on my system where the PXELINUX (and also the ISOLINUX) keep on prompting me the "Initial menu has no LABEL entries!" message, when vesamenu.c32 or menu.c32 is executed. After some investigation, I found that the global cm used in menu_main before it is initialized, and hence it carries a NULL value. I manage to get my system to display the menu after I
2014 Jun 24
0
Re: bridge could not be initialized
On Tue, Jun 24, 2014 at 05:24:01PM +0530, Kashyap Chamarthy wrote: > [Please keep the list in CC for technical questions.] Now adding the list for real. > > On Mon, Jun 23, 2014 at 04:45:25PM +0530, abhishek jain wrote: > > Hi > > > > I'm trying to run VM from controller node onto compute node and it is > > stucking at spawning state. > > There could
2014 Jul 24
0
Re: vhost-net requested but could not be initialized
For qemu, the default vhost drive file is “/dev/vhost-net”, when you configured vhost on. Give the command “modprobe vhost-net” to add host kernel support for vhost. This is cannot controlled by libvirt I think. Wangkai From: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] On Behalf Of Asadullah Hussain Sent: Thursday, July 24, 2014 12:43 AM To:
2014 Jul 24
0
Re: vhost-net requested but could not be initialized
On Thu, Jul 24, 2014 at 08:42:47AM +0500, Asadullah Hussain wrote: > Thanks Wangkai but libvirt infact pre-configures network tap devices and > pre-opens /dev/vhost-net file and passes these to qemu as open, ready to > use file descriptors. > > My issue is that my qemu requires that /dev/vhost-net directory is removed > and it's kernel module be unloaded. Then it creates a
2014 Jul 24
0
Re: vhost-net requested but could not be initialized
On 24 July 2014 15:52, Daniel P. Berrange <berrange@redhat.com> wrote: > On Thu, Jul 24, 2014 at 03:48:06PM +0500, Asadullah Hussain wrote: > > Let me clarify my question, I am using unmodified stock qemu (1.4.0) and > > only the location of vhost file descriptor is different from default (I > > don't remove the default /dev/vhost-net directory) > > > >
2005 Nov 02
1
[LLVMdev] Statically Initialized Arrays
On Nov 2, 2005, at 16:39, Chris Lattner wrote: > 4. Replace the old GV with the new GV using code that looks like this: > > OldGV->replaceAllUsesWith(ConstantExpr::getCast(NewGV, > OldGV->getType()); > OldGV->eraseFromParent(); > > At the end of this, any instructions or other globals that referenced > the temporary global will now reference the new one.
2006 Dec 09
2
[LLVMdev] [patch] emit .weak for zero initialized weak variables
The attached patches makes all backends print a .weak directive for zero initialized variables. GCC does it on x86-64 and ARM. I assume that it should be done on all architectures. The patch also adds a test to the ARM backend? Should I copy it to all backends? Comments? Thanks, Rafael P.S.: I find the doFinalization code a bit confusing. Would you welcome a cleanup patch? -------------- next
2006 Dec 16
0
[LLVMdev] [patch] emit .weak for zero initialized weak variables
On Sat, 9 Dec 2006, [UTF-8] Rafael Esp?ndola wrote: > The attached patches makes all backends print a .weak directive for > zero initialized variables. GCC does it on x86-64 and ARM. I assume > that it should be done on all architectures. > > The patch also adds a test to the ARM backend? Should I copy it to all > backends? I'm not sure this is right. C code like this:
2006 Dec 18
2
[LLVMdev] [patch] emit .weak for zero initialized weak variables
> I'm not sure this is right. C code like this: > > int X; > > should compile to a .comm directive, not a .weak directive, right? right. According to GCC, "int x" should compile to ".comm x", but "int x __attribute__((weak))" should compile to --------------- .weak x x: .zero 4 --------------- It looks like we have a bug in