search for: transacted

Seems currently xenstore transaction provides confusing message in different places: a) comment of xs_transaction_start says "You can only have one transaction at any time." However do_transaction_start allows up to 10 transactions created, as long as all other existing transaction channel is idle at the time (conn->transaction == NULL) b) when multiple transactions can be

Dovecot builds just fine, but fails the tests in src/lib-index. Note that reverting this commit fixes the issue: https://github.com/dovecot/core/commit/dfa4b048ec9a174a42d6668e94501db2fb70793a $ make check for bin in test-mail-index-map test-mail-index-modseq test-mail-index-sync-ext test-mail-index-transaction-finish test-mail-index-transaction-update test-mail-transaction-log-append

Hi, I sent a mail a few days ago to this list related with GFS+samba problems. Since the, we have installed a sepparated test environment also with two linux servers where we have tested a samba server with an exported share in GFS. The share is read-only and only one server is exporting it. When we try to access from a single windows client it works fine, but when we try to access to the

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158

Our support team seems to have caused another crash. They treat this mailbox like a shared one, so there may be a few people accessing it at once. They are mostly using dovecot, but some could be using uw-imap. These are the only two ways that this box is accessed. I know that this doesn't really work with mbox, but it doesn't appear to corrupt the mailbox. It seems to be a good stress

On 28.02.2017 06:14, Peter Ajamian wrote: > Dovecot builds just fine, but fails the tests in src/lib-index. > > Note that reverting this commit fixes the issue: > https://github.com/dovecot/core/commit/dfa4b048ec9a174a42d6668e94501db2fb70793a > > $ make check > for bin in test-mail-index-map test-mail-index-modseq > test-mail-index-sync-ext

Hey guys, I''m having a hard time w/ the after_update callback on rails... As far as I can tell, when I define a after_update callback on a model, the attributes of the object have the same values that they had *before* Base.save was called. I''m probably wrong so here''s the code: UNIT TEST: def test_register_item_adjusts_account_balance account =

If I want to wrap two account updates, the syntax is ... Account.transaction(dennis, david) do dennis.withdraw(10); david.deposit(10); end .. where both dennis and david are instances of Account. Can someone please let me know what the syntax is for starting and ending a *single* database transactions which spans two *different* kinds of models/tables ? Dennis Byrne -------------- next

I have dovecot-1.0-test64 installed on OpenBSD-3.6. It works fine with local password. Now I fail to get dovecot to use MySQL to query for user details. Any help would be very appreciated. Here are the details: from /var/log/maillog: 1) with "default_pass_scheme = PLAIN" Apr 3 07:20:22 www dovecot: Dovecot v1.0-test64 starting up Apr 3 07:20:23 www dovecot:

Hi, In Agile Web Development with Rails section on Transactions (p 381) there are two main examples. 1) making changes in two records in the same database table 2) making changes in two records each in a different *database* I want to do what is in between: changes in two records each in a different table of the same database. Suppose they are apples and oranges tables. How do I write this?

Hi, Does anyone knows how to manage transactions in RoR. Thanx

Hi All, I have the following arrangement: class PickAndPackRequest < ActiveRecord::Base has_many :transactions, :as => :request has_many :postings, :through => :transactions end class Transaction < ActiveRecord::Base belongs_to :request, :polymorphic => true has_many :postings end class Posting < ActiveRecord::Base belongs_to :transaction end But when I ask for

Hi Jan, I am now reading quota support in ocfs2 and have some qs. Wish you can help me clarify it. Thanks. ocfs2_quota_write: In the comment, you said that "we know the transaction is already started", so it should be called within a transaction. But in this function, we call ocfs2_extend_no_holes and ocfs2_simple_size_update which will start another transaction. So we can survive

I just tried to perform a yum upgrade on my CentOS 5 machine and it failed on a pm-utils >= 0.99.3-6 is needed by package hal error. I rsync my repos every night. This is the first time it's happened sudo yum -y upgrade Loading "installonlyn" plugin Loading "priorities" plugin Setting up Upgrade Process Setting up repositories updates 100%

Hello, I have an application where I need to create two records in a database transaction. ie: begin User.transaction(user) do User_details.transaction(user_details) do user.save user_details.save end end end rescue flash[:notice] "Insert rolled back... but why..??" end >From reading the Agile book, I gather that once I wrap the

In my application a user working at a dropzone can manipulate transactions against customer accounts. Here''s my models: class Transaction < ActiveRecord::Base belongs_to :account end class Account < ActiveRecord::Base belongs_to :dropzone has_many :transactions end class Dropzone < ActiveRecord::Base has_many :transactions, :through => :accounts do def

Hello! I experienced problems with testing transactions which are supposed to be rolled back, but are not, because of transactional fixtures eliminating the inner transaction. Can this be worked around somehow without turning off transactional fixtures? Maybe savepoints can help this? Does anyone have any experience with savepoints to achieve nested transaction functionality? Both Postgres

I''m trying to create a sequence with no gaps in my db (contrived example, but should work out the same as my real one), and believe db-managed transactions are the way to go about this. It''s my first real ''go'' at transactions, so I may be mistaken about how things really work. Anyway.. Consider this example code: Class Invoice < ActiveRecord::Base def

Hi I have two models Keyword and KeywordResult, they basically look like this: class KeywordResult < ActiveRecord::Base belongs_to :keyword validates_presence_of :title, :url, :keyword_id end class Keyword < ActiveRecord::Base has_many :keyword_results, :dependent => :delete_all acts_as_tree :order => "text", :foreign_key => "top_keyword" end Before you