|
|
Log in / Subscribe / Register

Nope...

Nope...

Posted Nov 21, 2011 21:08 UTC (Mon) by raven667 (subscriber, #5198)
In reply to: Nope... by khim
Parent article: That newfangled Journal thing

Well, there the reason that the webapp config is in a DB rather than text files is that this is easier and safer to read/write esp. when there may be multiple users changing settings at any given time. Sure you _could_ try and deal with multiple writers modifying config files while the app is continuously parsing and rereading the config to pick up changes but implementing all the custom parsing and locking is going to be a lot more difficult than writing a few simple select/insert/update/delete transactions.


to post comments

Nope...

Posted Nov 22, 2011 0:45 UTC (Tue) by dashesy (guest, #74652) [Link] (2 responses)

Very true, even for a single user.
It remembers me of trying to synchronize history across multiple open gnome terminals in a way that they do not step on each others feet!

Nope...

Posted Nov 22, 2011 16:58 UTC (Tue) by mathstuf (subscriber, #69389) [Link] (1 responses)

Share history among *running* terminals or make sure that all history gets to the histfile? I have zsh set up to do the latter (the shell's history gets appended to the global history; it doesn't overwrite the histfile with old history plus its history (which bash does)). It's just "setopt appendhistory".

Nope...

Posted Dec 1, 2011 12:54 UTC (Thu) by nye (subscriber, #51576) [Link]

>it doesn't overwrite the histfile with old history plus its history (which bash does)).

$ shopt -s histappend


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds