summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLihong <lihongx.sun@intel.com>2014-11-10 22:26:44 -0500
committeradmin <yuhuan.yang@samsung.com>2016-02-04 18:30:54 +0800
commit06fc0fe3d62494e09d97ba5215ca1dcd37d1c659 (patch)
treebb67991704c7636f6e2b1b06ef786c44f3d45737 /doc
parent00562876b3a5023639ce27b91251e8d8212167ad (diff)
downloadmic-06fc0fe3d62494e09d97ba5215ca1dcd37d1c659.tar.gz
mic-06fc0fe3d62494e09d97ba5215ca1dcd37d1c659.tar.bz2
mic-06fc0fe3d62494e09d97ba5215ca1dcd37d1c659.zip
Put log file in 'release' output always.
When image creation failed, log created by '--release' will be located under 'outdir' instead of 'release_dir'. Also put the log file under 'release_dir' when image creation failed. mic-appliance create images through executing '/etc/init.d/mic' script in the appliance. 'time mic cr auto $extra /media/out/$ks' is called, and '--release' option is used when creating images. In the past, 3 points about the logfile created by '--release': 1. Create logfile in default 'out_dir' which is specified in '/etc/mic/mic.conf'. 2. Before creating images, check whether the 'release_dir' exists, if it exists, remove the whole directory. 3. After the image creation finished, copy the logfile to the final 'release_dir' where the images located. So when the image creation failed, no logfile found in 'release_dir', the logfile is under default 'out_dir'. If directly change the 'out_dir' to 'dest_dir' in conf.py, the image creation will fail if there already exist a same 'release_dir', because this existed 'release_dir' will be removed when creating images, but the logfile use this dir at the time, so it cannot be removed, then mic will fail and exit. So right now, if 'release_dir' already existed, just remove the files under it except the newly created logfile, and remain the dir. Fixes: #2212 Change-Id: Ibdc9af3d0e03ca966517d05b1e519d4d9fb3ad43
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions