search for: syslogger

...onfused by the RHEL release notes and an earlier thread here about rsyslogd, so I hope someone can clear this up for me; I see that rsyslog is included in RHEL as of 5.2 (and so will be available in CentOS when 5.2 is ready) however there is no indication of whether it has been made the default syslogger or not - is it an optional package or installed by default on a fresh install? (I would check myself, but I do not have any RHEL5 machines to hand.) Thanks -Laurence

...new drive as /var2, cp -R (in hindsight should had rsync to preserve attributes), deleted the original /var to free up space, edited fstab and rebooted... unsurprisingly to a fubar'd server. The thing is it still boots, I can get into single user mode but a full init get stuck at starting the syslogger. What is the best way to rescue the server now from my own stupidity and keeping all the existing configuration and data?

Is it possible to send logs to syslog and files set by log_path and log_info_path on config? Just two logs at the same time (not realtime). -- Antonio P?rez-Aranda Alcaide aperezaranda at yaco.es Yaco Sistemas S.L. http://www.yaco.es/ C/ Rioja 5, 41001 Sevilla Tel?fono +34 954 50 00 57 Fax ? ? ?+34 954 50 09 29

Hello! I'm using LLVM's JIT in my project. Is there any way to view assembly code of functions it generates without disassembling them from the memory?

Hi all, I''ve been using SyslogLogger to do standard application logging and it works great. I want to do my custom application logging to a seperate log but I''m having problems. I create the default application logger with SyslogLogger.new (leaving it with the the default application name) my second instance of the SyslogLogger I pass it the name custom_app_log. Now in my

When using LLVM as a JIT compiler, you can use module.dump() to show the generated intermediate code, which is good. Is there similarly a programmatic way to show the generated x64 machine code in assembly format? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160406/c7d22dab/attachment.html>

...of JFS records were flooding the syslog server and causing it to back up, blocking further attemtps to write to syslog while the back up was being flushed to disk. Every startup script uses initlog to write the output of the startup to syslog, so the scripts immediatley following the start of the syslogger were blocking, presumably due to syslogd's buffer being full. b.

On Thu, Sep 3, 2015 at 6:45 PM, Kostya Serebryany <kcc at google.com> wrote: > Did you build the Postgres code with -fsanitize-coverage=... ? Yes: CC = clang CFLAGS = -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -Wno-unused-command-line-argument -g -O0 -fsanitize=address

...port/dynloader.o port/pg_sema.o > port/pg_shmem.o port/pg_latch.o postmaster/autovacuum.o > postmaster/bgworker.o postmaster/bgwriter.o postmaster/checkpointer.o > postmaster/fork_process.o postmaster/pgarch.o postmaster/pgstat.o > postmaster/postmaster.o postmaster/startup.o postmaster/syslogger.o > postmaster/walwriter.o regex/regcomp.o regex/regerror.o > regex/regexec.o regex/regfree.o regex/regprefix.o regex/regexport.o > replication/logical/decode.o replication/logical/logical.o > replication/logical/logicalfuncs.o replication/logical/reorderbuffer.o > replication/logica...