summaryrefslogtreecommitdiff
path: root/meta/conf/machine/mx31phy.conf
diff options
context:
space:
mode:
authorKevin Tian <kevin.tian@intel.com>2010-06-21 17:28:57 +0800
committerKevin Tian <kevin.tian@intel.com>2010-07-02 17:27:10 +0800
commite96dc90ba443601116eed52873da2ea929af726e (patch)
treeaf9351107b6209658b8f85f498bcc328a5501d28 /meta/conf/machine/mx31phy.conf
parent968d00de157bcc614cc7c47a4a36db29d677ab89 (diff)
downloadopenembedded-core-e96dc90ba443601116eed52873da2ea929af726e.tar.gz
openembedded-core-e96dc90ba443601116eed52873da2ea929af726e.tar.bz2
openembedded-core-e96dc90ba443601116eed52873da2ea929af726e.tar.xz
openembedded-core-e96dc90ba443601116eed52873da2ea929af726e.zip
populate-volatile.sh: add "clearcache" cmdline option
Sometimes /etc/volatiles.cache is corrupted when Qemu gets crashed. Current logic is to always execute cache file as long as it exists. When it's currupted, this causes core volatile files/directories not created and then prevent many important services from starting. Automatic check on cache goodness is one option. However it's not easy since the currupted file could be various states. In one form, it's full of zeros. In another form, some commands are truncated. Here allow a cmdline option to force removing volatiles.cache file, since it's easy for user to check whether the cache file is mal-formed. Usually you'll observe typical directories like "/var/log/" or "/var/run" not found error. Signed-off-by Kevin Tian <kevin.tian@intel.com>
Diffstat (limited to 'meta/conf/machine/mx31phy.conf')
0 files changed, 0 insertions, 0 deletions