lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Fri, 17 Jun 2011 13:42:25 +0200
From:	Tomasz Chmielewski <mangoo@...g.org>
To:	linux-kernel@...r.kernel.org
Subject: change kernel logging (console=ttyS0) without reboot?

Generally, most production systems don't like to be restarted unnecessarily.

I was wondering if it's possible to change kernel logging without a restart?

Say, I connected a serial cable to the server, but kernel was not booted 
with anything like console=ttyS0,19200 in its command line. So anything 
produced by the kernel will not show up on ttyS0.


Can I still somehow make the kernel to log to ttyS0, without restarting 
it (I can make syslog do it, but let's assume the syslog crashed and I'm 
mostly interested in catching a kernel oops/panic etc.)?



-- 
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ