Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
12-23-2014, 08:45 PM
|
#1
|
Member
Registered: Apr 2011
Location: Minneapolis
Distribution: CentOS 7
Posts: 80
Rep:
|
centos 7: how to manually start a new system log?
The system log is in /var/log/system. It can grow large, and being on an unstable system, I'd like to recreate the error on a smaller log file before posting it. Is there a way for me to manually initiate the use of a new system log file?
Thanks,
|
|
|
12-23-2014, 08:57 PM
|
#2
|
LQ Guru
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,986
|
Do you have logrotate installed? It should help manage the size of the log files.
If this is an error you can reproduce at will, you could run
Code:
tail -f /var/log/[somelog]
and capture the output to the console as the error is logged.
Edit:
I just learned about this command in this thread. It may do what you want.
Last edited by frankbell; 12-23-2014 at 09:25 PM.
Reason: More information
|
|
|
12-26-2014, 06:55 PM
|
#3
|
LQ Newbie
Registered: Dec 2014
Posts: 3
Rep: 
|
Either use the "tail -f" as suggested above, or ...
mv -f /var/log/system /tmp/old_system_log; killall -HUP <syslog_process>
Hope this helps,
|
|
|
12-26-2014, 07:20 PM
|
#4
|
Senior Member
Registered: Mar 2010
Distribution: Slackware
Posts: 2,280
|
/var/run/syslogd.pid contains the process id of syslogd. Every month I kill that process, rename /var/log/syslog and the other log files to which syslogd writes, adding the year and month, e.g. syslog becomes syslog-201412, then start syslogd again. On my distribution I can use /etc/rc.d/rc.syslog to start and stop syslogd, but that's unnecessary.
I reserve syslog for the most important system information by separating non-essential stuff into separate log files, most importantly the dhcp stuff (and lynx, for me, but who else uses that anymore?). I did the same for acpi and apm back when I had them.
|
|
|
All times are GMT -5. The time now is 09:46 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|