journal

I have a large journal file with date entries like this: [2011-06-23 Thu] some text [2011-06-22 Wed] some more text [... 12MB of text later ...] [2000-01-01 Sat] first entry I would like to be able to configure org-mode so that only the last 3 months are visible, whereas older entries are collapsed, and are only expanded when I need to. Is there a way of setting this up automatically so that every new day makes the 3 month + 1 day old entry be collapsed next time? As it is now, it's impossible for me to use, because it takes more than a minute to load the document. phils With 12MB of text,

In my andoid application's database directory (/data/data/com.me.myApp/databases), for every sqlite database I create there is a corresponding database of the same name with "-journal" appended to it's name. e.g: myDatabase, myDatabase-journal, myOtherDatabase.db, myOtherDatabase.db-journal What is this? and, If I'm providing pre-filled databases for my app (as per: http://www.reigndesign.com/blog/using-your-own-sqlite-database-in-android-applications/ ) do I need to include these as well?' Such -journal files do not need to (and should not ) be distributed. This is because the various journal

NameNode之间共享数据 （NFS 、 Quorum Journal Node（用得多） ） 两个NameNode为了数据同步，会通过一组称作JournalNodes的独立进程进行相互通信。当active状态的NameNode的命名空间有任何修改时，会告知大部分的JournalNodes进程。standby状态的NameNode有能力读取JNs中的变更信息，并且一直监控edit log的变化，把变化应用于自己的命名空间。standby可以确保在集群出错时，命名空间状态已经完全同步了。 Hadoop 中的NameNode好比是人的心脏，非常重要，绝对不可以停止工作 。在hadoop1时代，只有一个NameNode。如果该NameNode数据丢失或者不能工作，那么整个集群就不能恢复了。这是hadoop1中的单点问题，也是hadoop1不可靠的表现，如图1所示。hadoop2就解决了这个问题。 图1 hadoop2.2.0（HA）中HDFS的高可靠指的 是可以同时启动2个NameNode。其中一个处于工作状态，另一个处于随时待命状态。这样，当一个NameNode所在的服务器宕机时，可以在数据不丢失的情况下， 手工 或者 自动 切换到另一个NameNode提供服务。 这些 NameNode之间通过共享数据，保证数据的状态一致。多个NameNode之间共享数据，可以通过Nnetwork

I am using transactions to insert multiple rows into table. But, I still see temporary sqlite-journal file being created on SD Card along with sqlite table. How do I disable creation of journal file? Thanks You can elect to keep the journal in memory so that no -journal file is created: pragma journal_mode=memory; Note that you need to run this each time you open the database. I recommend that you read the following to get a better idea of what is going on: http://www.sqlite.org/pragma.html#pragma_journal_mode The journal is an internal SQLite file that is used when running transactions (to