From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,NICE_REPLY_A autolearn=ham autolearn_force=no version=3.4.4 Received: from alyss.skarnet.org (alyss.skarnet.org [95.142.172.232]) by inbox.vuxu.org (Postfix) with SMTP id 591F130C10 for ; Sat, 7 Dec 2024 16:19:17 +0100 (CET) Received: (qmail 32205 invoked by uid 89); 7 Dec 2024 15:19:43 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 32198 invoked from network); 7 Dec 2024 15:19:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freesa.org; s=20240917; t=1733584754; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fQDzVkct6RDrZLeYM1rzE9SVLB30FCltFPz1wIo2INc=; b=idAyCQr3e4iJ7XRvaHhBKYnvljS0eG78wcfWZaZVgepcIuJNbIY016khrYBAMEGQ+UqxlJ wiVahVwOBLn5qSCp0PFN5D5euVKXJOyaqF+z3qw/FOgcfRgMvEAKav+7zKIC6EzqNrphV+ juNXCvpVKHTs5eGdMWvlisRuQdJHuMk= Date: Sat, 7 Dec 2024 09:19:08 -0600 From: "Brett Neumeier via supervision" Reply-To: Brett Neumeier To: "supervision@list.skarnet.org" Subject: Re: Mysqld logs Message-Id: <20241207091908.21b7bed2ec1e061c4aec7be1@freesa.org> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sat, 7 Dec 2024 15:40:30 +0100 Paul Sopka wrote: > Hey everybody >=20 > From what I could find, mysqld, a server deamon for mysql, > seems to only be able to output logs to files. > Is it a bad idea to run it in the following way? >=20 > =A0=A0=A0 mysqld --log_error=3D/dev/stdout >=20 > e.g. in that there any Unix you know about that does not support=20 > /dev/stdout? I don't know of any. If you're concerned, though, you can always create a FIFO and write log output to it, and then read from that FIFO in your logging service. That's my common practice when a program prefers to write log messages to a file. (Or when I set up a program to write to several different logs, like nginx.) One thing, though -- MariaDB is the fork of MySQL that I use, and it has a `--console` option that causes those messages to be written to stdout already. Perhaps MySQL has that option as well? That would be even simpler. Cheers, Brett --=20 Brett Neumeier