supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Brett Neumeier via supervision" <supervision@list.skarnet.org>
To: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: Re: Mysqld logs
Date: Sat, 7 Dec 2024 09:19:08 -0600	[thread overview]
Message-ID: <20241207091908.21b7bed2ec1e061c4aec7be1@freesa.org> (raw)
In-Reply-To: <d7c23d45-51ce-496e-ac71-eb6e82d87a74@sopka.ch>

On Sat, 7 Dec 2024 15:40:30 +0100
Paul Sopka <psopka@sopka.ch> wrote:

> Hey everybody
> 
>  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?
> 
>      mysqld --log_error=/dev/stdout
> 
> e.g. in that there any Unix you know about that does not support 
> /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

-- 
Brett Neumeier <random@freesa.org>

  reply	other threads:[~2024-12-07 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-07 14:40 Paul Sopka
2024-12-07 15:19 ` Brett Neumeier via supervision [this message]
2024-12-07 15:34   ` Paul Sopka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241207091908.21b7bed2ec1e061c4aec7be1@freesa.org \
    --to=supervision@list.skarnet.org \
    --cc=random@freesa.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).