From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 61E39C54EAA for ; Mon, 30 Jan 2023 16:21:04 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.96) (envelope-from ) id 1pMWtj-0002dN-38; Mon, 30 Jan 2023 11:20:47 -0500 Received: from mail-4316.protonmail.ch ([185.70.43.16]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1pMWth-0002bi-0k for kernelnewbies@kernelnewbies.org; Mon, 30 Jan 2023 11:20:45 -0500 Date: Mon, 30 Jan 2023 16:20:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pm.me; s=protonmail3; t=1675095642; x=1675354842; bh=IPpkhUfyN1XVDl2COKHHdVLNmLURE1m4+n7xHbuDFlc=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=TS1Sdo9mWe43qDlglE8rbGnL4/IaKKV/wk6qvYB8mF431vDokVRXM/3ItmW+bPp9z WiflJRFsj5AaFks1vjF6kjeA22T+GO57j4WXZTM8zpMyB1BJu4/Igwf5w4JTCcAOCX zUpOSKA2RffQ0QvJrCE+UWualKnRavdDv3+q9/DlCF+iowy+AXwrOlVTiqZ2roR6bx YZqFW0ftXlTbRxhKhvR9oKYgdzWz7njV7QCXsagrcZjyYwP1EXV0L0EwAszXRjEGY9 UmJmXyFyoVjch0P/b3grrnuKQdCO6uPlTS5tcPwjN+SQEezcnDzQTSVMTd518FsfJR XFlo1M6IYqg/w== To: kernelnewbies@kernelnewbies.org From: "Axel M." Subject: uninterruptible process Message-ID: Feedback-ID: 40529128:user:proton MIME-Version: 1.0 X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org Hi all, I'm looking for system call that can make my process uninterrupted until it completes successfully. My app receives a SIGTERM signal (when an shutdown is triggerd), then needs to write into a file with a simple fopen(). Actually it can't write in my file because I think it is automatically killed (SIGKILL) by systemd. Do you have any advice on this ? Thanks -- Thanks, Axel M. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies