Sponsored Content
Operating Systems Linux SuSE Location and name of SYSLOG in SUSE Linux Post 302937825 by cjcox on Monday 9th of March 2015 05:59:21 PM
Old 03-09-2015
On newer SUSE and openSUSE systems, they use systemd. You can install rsyslog and get a /var/log/messages file (for example) and/or the ability to send logs to a remote syslogger, etc...

It's one of the bigger gripes against systemd. It uses its own binary database to house logs. So normally you run a command, journalctl, (if you don't have rsyslog installed) to see the logs.
This User Gave Thanks to cjcox For This Post:
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

suse linux 6.4-8.1

i need some help from somone familiar with suse linux. i am wanting to update my suse linux 6.4 box to suse linux 8.1. i am trying to do it with yast. and i want to do it via ftp. now, to do this the first thing i need to do is change my source media settings in yast, right now it is the cdrom.... (3 Replies)
Discussion started by: norsk hedensk
3 Replies

2. SuSE

Suse LINUX

What is the equivalent of sun explorer in suse linux? Thanks (1 Reply)
Discussion started by: hassan2
1 Replies

3. Linux

SUSE Linux

i'm new linux ... after reboot ...... my keyboard is notworking automatically boot ..... after few mins Waiting for mandatory devices: eth-id-00:10:a7:08:cb:4b 12 11 9 8 7 5 4 3 1 0 eth0 interface could not be set up failed Setting up service network . . . . . . . . . . . . . ... (2 Replies)
Discussion started by: coolboys
2 Replies
SAVE_BINARY_LOGS(1p)					User Contributed Perl Documentation				      SAVE_BINARY_LOGS(1p)

NAME
save_binary_logs - Concatenating binary or relay logs from the specified file/position to the end of the log. This command is automatically executed from MHA Manager on failover, and manual execution should not be needed normally. SYNOPSIS
# Test $ save_binary_logs --command=test --binlog_dir=/var/lib/mysql --start_file=mysqld-bin.000002 # Saving binary logs $ save_binary_logs --command=save --binlog_dir=/var/lib/mysql --start_file=mysqld-bin.000002 --start_pos=312 --output_file=/var/tmp/aggregate.binlog # Saving relay logs $ save_binary_logs --command=save --start_file=mysqld-relay-bin.000002 --start_pos=312 --relay_log_info=/var/lib/mysql/relay-log.info --output_file=/var/tmp/aggregate.binlog save_binary_logs concatenates binary or relay logs from the specified log file/position to the end of the log. This tool is intended to be invoked from the master failover script(MHA Manager), and manual execution is normally not needed. DESCRIPTION
Suppose that master is crashed and the latest slave server has received binary logs up to mysqld-bin.000002:312. It is likely that master has more binary logs. If it is not sent to the slave, slaves will lose all binlogs from mysqld-bin.000002:312. The purpose of the save_binary_logs is to save binary logs that are not replicated to slaves. If master is reachable through SSH and binary logs are readable, saving binary logs is possible. Here is an example: $ save_binary_logs --command=save --start_file=mysqld-bin.000002 --start_pos=312 --output_file=/var/tmp/aggregate.binlog Then all binary logs starting from mysqld-bin.000002:312 are concatenated and stored into /var/tmp/aggregate.binlog. If you have binary logs up to mysqld-bin.000004, the following mysqlbinlog outputs are written. mysqld-bin.000002:Format Description Event(FDE), plus from 312 to the tail mysqld-bin.000003:from 0 to the tail, excluding FDE mysqld-bin.000004:from 0 to the tail, excluding FDE perl v5.14.2 2012-01-08 SAVE_BINARY_LOGS(1p)
All times are GMT -4. The time now is 03:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy