dump_systemstate: Wait for buxton to really start 35/302335/4 accepted/tizen_unified_toolchain accepted/tizen/unified/20240430.020606 accepted/tizen/unified/toolchain/20240507.011851 accepted/tizen/unified/x/20240430.094809
authorKarol Lewandowski <k.lewandowsk@samsung.com>
Tue, 5 Dec 2023 09:44:47 +0000 (10:44 +0100)
committerKarol Lewandowski <k.lewandowsk@samsung.com>
Fri, 26 Apr 2024 14:37:38 +0000 (16:37 +0200)
commitdeeb379d48f24372e317e59057f4e27842f89581
tree6e938123b458e4f5565784f50a5bded0b21a0c71
parent5b23948acc859625eb99322aed3673fe92af7d24
dump_systemstate: Wait for buxton to really start

Otherwise crash_worker will directly access sqlite database, and create its tmp/journal
files with inappropriate (crash_worker) user and group - consequently breaking access
to the files to buxton service itself and rest of the system.

Change-Id: I7be39c433efa39effb07b5714d6a5e773b68e15d
packaging/crash-worker.spec
src/dump_systemstate/BUGS [new file with mode: 0644]
src/dump_systemstate/CMakeLists.txt
src/dump_systemstate/helpers/buxton-wait [new file with mode: 0755]
src/dump_systemstate/programs/crash-worker-programs.conf