Fix sample engine latest updated time as installing time 28/145428/2 accepted/tizen/4.0/unified/20170828.222318 accepted/tizen/unified/20170823.170303 submit/tizen/20170823.025619 submit/tizen_4.0/20170828.100005 tizen_4.0.IoT.p1_release tizen_4.0.IoT.p2_release tizen_4.0.m2_release
authorsangwan.kwon <sangwan.kwon@samsung.com>
Tue, 22 Aug 2017 06:44:51 +0000 (02:44 -0400)
committersangwan kwon <sangwan.kwon@samsung.com>
Tue, 22 Aug 2017 08:44:26 +0000 (08:44 +0000)
Malware detected time should greater than engine's latest update time
when engine is not updated after malware detecting. But some device's
current time is not correct(before: 2016) and sample engine's latest
updated time is fixed time(after: 2017), some TC was always failed.

Change-Id: I34ec53e612eb927ae0c2261a1ba4f42af6a7fb51
Signed-off-by: sangwan.kwon <sangwan.kwon@samsung.com>
packaging/csr-framework.spec

index cdd54af..d455bec 100644 (file)
@@ -246,6 +246,9 @@ systemctl stop %{service_name}-cs.socket
 systemctl stop %{service_name}-wp.socket
 systemctl stop %{service_name}-admin.socket
 systemctl restart %{service_name}.service
+
+touch %{engine_rw_working_dir}/csret_cs_virus_signatures
+touch %{engine_rw_working_dir}/csret_wp_risky_urls
 %endif
 
 %files -f %{service_name}.lang