search for: otherweise

Displaying 15 results from an estimated 15 matches for "otherweise".

Did you mean: otherewise
2011 Oct 28
6
dsync should sync sieve-dirs to!
Having dsync to make backups from existing mail-spaces, it would be nice to make dsync syncing the sieve-dirs too. -Otherweise backups aren't complete... Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Gesch?ftsf?hrer:...
2016 Mar 02
3
VM's in a HA-configuration - synchronising vm config files
...vm's are stored on a FC SAN, so every host has access to the vm's. But how can i keep the config files (xml-files under /etc/libvirt/qemu) synchronised ? Is there a possibility to store the config files somewhere else ? E.g. a partitition with ocfs2 on the SAN ? If not, what would you do ? Otherweise i'm thinking of a cron-job who synchronises the file each minute with rsync. Bernd -- Bernd Lentes Systemadministration institute of developmental genetics Gebäude 35.34 - Raum 208 HelmholtzZentrum München bernd.lentes@helmholtz-muenchen.de phone: +49 (0)89 3187 1241 fax: +49 (0)8...
2008 Jul 11
1
Scriptaculous: how to keep element space?
Hello everybody, I hope I am at the right place here with my question, otherweise please accept my apologies. I searched a lot for my question and did not find an answer, so I would be very happy if you could help me out maybe. I am using Effect.Fade for on element. Everythings works fine, but when the element is faded out, its space it no longer used and therefore other eleme...
2016 Mar 02
1
Re: VM's in a HA-configuration - synchronising vm config files
...every host has access to the vm's. >>But how can i keep the config files >(xml-files under /etc/libvirt/qemu) >>synchronised ? Is there a possibility to store the config files somewhere else >>? E.g. a partitition with ocfs2 on the SAN ? >>If not, what would you do ? Otherweise i'm thinking of a cron-job who >>synchronises the file each minute with rsync. >> >> >>Bernd >> >>-- > > This looks simple enough... > > On host 1, virsh dumpxml for every running vm to a shared location > On host 2, virsh define for these vm...
2013 Jan 30
2
recoding variables again :(
Ein eingebundener Text mit undefiniertem Zeichensatz wurde abgetrennt. Name: nicht verf?gbar URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20130130/7bc4cd37/attachment.pl>
2016 Mar 02
0
Re: VM's in a HA-configuration - synchronising vm config files
...s are stored on a FC SAN, so every host has access to the vm's. But how can i keep the config files >(xml-files under /etc/libvirt/qemu) synchronised ? Is there a possibility to store the config files somewhere else ? E.g. a partitition with ocfs2 on the SAN ? >If not, what would you do ? Otherweise i'm thinking of a cron-job who synchronises the file each minute with rsync. > > >Bernd > >-- This looks simple enough... On host 1, virsh dumpxml for every running vm to a shared location On host 2, virsh define for these vm's Do the same the other way around...
2016 Apr 01
2
[PATCH v3 03/16] mm: add non-lru movable page support document
...> +Note about releasing page: > + > +Subsystem can release pages whenever it want but if it releses the page > +which is already isolated, it should clear PG_isolated but doesn't touch > +PG_movable under PG_lock. Instead of it, VM will clear PG_movable after > +his job done. Otherweise, subsystem should clear both page flags before > +releasing the page. I don't understand this right now. But maybe I will get it after reading the patches and suggest some improved wording here. > + > +Note about PG_isolated: > + > +PG_isolated check on a page is valid only if...
2016 Apr 01
2
[PATCH v3 03/16] mm: add non-lru movable page support document
...> +Note about releasing page: > + > +Subsystem can release pages whenever it want but if it releses the page > +which is already isolated, it should clear PG_isolated but doesn't touch > +PG_movable under PG_lock. Instead of it, VM will clear PG_movable after > +his job done. Otherweise, subsystem should clear both page flags before > +releasing the page. I don't understand this right now. But maybe I will get it after reading the patches and suggest some improved wording here. > + > +Note about PG_isolated: > + > +PG_isolated check on a page is valid only if...
2014 Aug 31
4
[Bug 2269] New: ssh-copy-id: does not respect .ssh/config
...Linux) : tfoerste at n22 ~ $ cat .ssh/config Host n22kvm IdentityFile=/home/tfoerste/.ssh/id_rsa-kvm Host n22stab4 IdentityFile=/home/tfoerste/.ssh/id_rsa-uml I#d expect, that ssh-copy-id would not transfer id-rs.pub to n22kvm when I run, but in fact I have to explicite?y specify the public key otherweise ssh-key-based login to n22kvm won't work. $> ssh-copy-id -i ~/.ssh/id_rsa-kvm.pub root at n22kvm Because ssh itself respects the config values I'm wondering if this is a bug or a feature ? -- You are receiving this mail because: You are watching the assignee of the bug.
2016 Mar 30
0
[PATCH v3 03/16] mm: add non-lru movable page support document
...as marked in isolation step. + +Note about releasing page: + +Subsystem can release pages whenever it want but if it releses the page +which is already isolated, it should clear PG_isolated but doesn't touch +PG_movable under PG_lock. Instead of it, VM will clear PG_movable after +his job done. Otherweise, subsystem should clear both page flags before +releasing the page. + +Note about PG_isolated: + +PG_isolated check on a page is valid only if the page's flag is already +set to PG_movable. + +Christoph Lameter, May 8, 2006. +Minchan Kim, Mar 28, 2016. -- 1.9.1
2016 Apr 04
1
[PATCH v3 03/16] mm: add non-lru movable page support document
...t;> + >>> +Subsystem can release pages whenever it want but if it releses the page >>> +which is already isolated, it should clear PG_isolated but doesn't touch >>> +PG_movable under PG_lock. Instead of it, VM will clear PG_movable after >>> +his job done. Otherweise, subsystem should clear both page flags before >>> +releasing the page. >> >> I don't understand this right now. But maybe I will get it after >> reading the patches and suggest some improved wording here. > > I will try to explain why such rule happens in there...
2016 Apr 04
1
[PATCH v3 03/16] mm: add non-lru movable page support document
...t;> + >>> +Subsystem can release pages whenever it want but if it releses the page >>> +which is already isolated, it should clear PG_isolated but doesn't touch >>> +PG_movable under PG_lock. Instead of it, VM will clear PG_movable after >>> +his job done. Otherweise, subsystem should clear both page flags before >>> +releasing the page. >> >> I don't understand this right now. But maybe I will get it after >> reading the patches and suggest some improved wording here. > > I will try to explain why such rule happens in there...
2016 Apr 04
0
[PATCH v3 03/16] mm: add non-lru movable page support document
...leasing page: > >+ > >+Subsystem can release pages whenever it want but if it releses the page > >+which is already isolated, it should clear PG_isolated but doesn't touch > >+PG_movable under PG_lock. Instead of it, VM will clear PG_movable after > >+his job done. Otherweise, subsystem should clear both page flags before > >+releasing the page. > > I don't understand this right now. But maybe I will get it after > reading the patches and suggest some improved wording here. I will try to explain why such rule happens in there. The problem is that p...
2016 Mar 30
33
[PATCH v3 00/16] Support non-lru page migration
Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.
2016 Mar 30
33
[PATCH v3 00/16] Support non-lru page migration
Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.