Changes to my logrotate.conf file do I need to reboot?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Changes to my logrotate.conf file do I need to reboot?
Using RHEL 5 and change my logrotate.conf file and restart service auditd. In order for my changes to take effect when I modified my logrotate.conf file do I need to reboot my RHEL 5 system?
As far as I know, logrotate is not a daemon that you restart but it's a process called from cron as a daily job. So there is nothing to restart. At the next scheduled run your config should be used when the logrotate process runs.
Of course if you want to run it to test your config then you can. It should be in /usr/sbin; so:
Code:
/usr/sbin/logrotate /etc/logrotate.conf
(if that's the location of your configuration file) should start it manually. And the next run will be triggered by the daily cron.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
The answer by EricTRA is correct. Besides, you should forget about rebooting as something to be done after changes are made. Rebooting is only needed when you install a new kernel, or have messed up your loaded modules down to the point where you lose that much functionality that you cannot reload them.
The answer by EricTRA is correct. Besides, you should forget about rebooting as something to be done after changes are made. Rebooting is only needed when you install a new kernel, or have messed up your loaded modules down to the point where you lose that much functionality that you cannot reload them.
jlinkels
Yeah, rebooting is something that belongs in the Microsoft world (have to do it on a weekly basis to keep those darn things running) whilst in LinuxLand it's rarely needed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.