Restricting Periodic Scripts
I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? -- Tim Gustafson t...@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Restricting Periodic Scripts
On Wed, 6 Feb 2013 09:26:17 -0800, Tim Gustafson wrote: I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? You can disable them per /etc/periodic.conf (see examples in /etc/defaults/periodic.conf). To keep the functionality, but restrict it to a smaller amount of files, you could use the system's scripts as templates, make your own derivates (wich inclusion or exclusion rules) and place them in /usr/local/etc/periodic for the system to call them (which it will if they are present). You can add your custom configuration flags to /etc/periodic.conf and have your scripts source that file (like the system's scripts do). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Restricting Periodic Scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/6/13 12:26 PM, Tim Gustafson wrote: I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? Hi Tim, Have a look at this posting from 2012: http://forums.freebsd.org/archive/index.php/t-31846.html There is a patch for the script in there, but I didn't check to see if the author ever filed a PR. There's also a workaround that involves using the nosuid mount option, if that is acceptable in your environment. Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlESmkAACgkQ0sRouByUApB2kgCfalTZRa5GQlAZjcNXq5qxfA3e 2rwAoLCMoscJYLVuevYLjZGj9qYiIjZD =3yUC -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Restricting Periodic Scripts
I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? Thanks to everyone who replied. I got some helpful suggestions from a few people, which all amounted to either disable the jobs or create your own custom version of those jobs. So for now, I'm just disabling them. I appreciate all the help. Thanks! -- Tim Gustafson t...@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
does anyone care about periodic scripts?
Hi all. It seems that patches to periodic scripts have hard time coming into the tree. I personally filed http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/165817 and still there's no move despite change is purely cosmetical and just fixes right way of things. And this is not just one and only case, pr's are numerous and get minimal to no attention at all: http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/165956 http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/30938 How can I assist with this pr's? Whom should I bug to get some answer about them? -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stop all manner of periodic scripts from running
Chuck Swiger wrote: On Mar 17, 2009, at 5:09 PM, Steve Bertrand wrote: Although SMTP is denied, I just realized that there are numerous messages from periodic scripts that are queued up that can't be sent. Can someone advise how to find out each and every periodic script that tries to send out email (given a standard install), and/or how to disable this? Besides the answer to disable sendmail listening on localhost, consider the following to /etc/periodic.conf: daily_clean_hoststat_enable=NO daily_status_mail_rejects_enable=NO daily_status_include_submit_mailq=NO daily_submit_queuerun=NO In answer to the principal question: just divert the periodic script output to a log file: daily_output=/var/log/daily.log daily_status_security_output=/var/log/daily.log weekly_output=/var/log/weekly.log monthly_output=/var/log/monthly.log You'll find those file names are already setup for appropriate log rotations in /etc/newsyslog.conf In the default install, the only things that generate e-mail are the periodic cron jobs, so this change should be all that is necessary. If you have set up your own cron jobs, then you'll have to be careful to redirect all output /dev/null 21 or else set a MAILTO variable in each crontab directing any output to an address that won't send mail outside the specific box. Perhaps something aliased to /dev/null even. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Stop all manner of periodic scripts from running
Matthew Seaman wrote: Chuck Swiger wrote: On Mar 17, 2009, at 5:09 PM, Steve Bertrand wrote: Although SMTP is denied, I just realized that there are numerous messages from periodic scripts that are queued up that can't be sent. Can someone advise how to find out each and every periodic script that tries to send out email (given a standard install), and/or how to disable this? Besides the answer to disable sendmail listening on localhost, consider the following to /etc/periodic.conf: daily_clean_hoststat_enable=NO daily_status_mail_rejects_enable=NO daily_status_include_submit_mailq=NO daily_submit_queuerun=NO In answer to the principal question: just divert the periodic script output to a log file: daily_output=/var/log/daily.log daily_status_security_output=/var/log/daily.log weekly_output=/var/log/weekly.log monthly_output=/var/log/monthly.log You'll find those file names are already setup for appropriate log rotations in /etc/newsyslog.conf In the default install, the only things that generate e-mail are the periodic cron jobs, so this change should be all that is necessary. If you have set up your own cron jobs, then you'll have to be careful to redirect all output /dev/null 21 or else set a MAILTO variable in each crontab directing any output to an address that won't send mail outside the specific box. Perhaps something aliased to /dev/null even. Thanks to all who responded. Not only do the methods do what I wanted, I also have quite a bit of flexibility. Cheers! Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stop all manner of periodic scripts from running
Hi everyone, Taking the questions regarding my routing boxes one step further, I have strict rules that allow only certain control and management protocols to communicate on the network. Although SMTP is denied, I just realized that there are numerous messages from periodic scripts that are queued up that can't be sent. Can someone advise how to find out each and every periodic script that tries to send out email (given a standard install), and/or how to disable this? Or, is there a way to completely cripple a FreeBSD machine, so the system actually realizes that it can not send any email, and everything it tries to send email will realize this? (preferably a more subtle approach than simply rm'ing the sendmail binary :) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stop all manner of periodic scripts from running
On Tue, Mar 17, 2009 at 8:09 PM, Steve Bertrand st...@ibctech.ca wrote: Hi everyone, Taking the questions regarding my routing boxes one step further, I have strict rules that allow only certain control and management protocols to communicate on the network. Although SMTP is denied, I just realized that there are numerous messages from periodic scripts that are queued up that can't be sent. Can someone advise how to find out each and every periodic script that tries to send out email (given a standard install), and/or how to disable this? Or, is there a way to completely cripple a FreeBSD machine, so the system actually realizes that it can not send any email, and everything it tries to send email will realize this? (preferably a more subtle approach than simply rm'ing the sendmail binary :) echo 'sendmail_enable=NONE' /etc/rc.conf -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Stop all manner of periodic scripts from running
On Mar 17, 2009, at 5:09 PM, Steve Bertrand wrote: Although SMTP is denied, I just realized that there are numerous messages from periodic scripts that are queued up that can't be sent. Can someone advise how to find out each and every periodic script that tries to send out email (given a standard install), and/or how to disable this? Besides the answer to disable sendmail listening on localhost, consider the following to /etc/periodic.conf: daily_clean_hoststat_enable=NO daily_status_mail_rejects_enable=NO daily_status_include_submit_mailq=NO daily_submit_queuerun=NO Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Changing 'From:' address of periodic scripts
Jonathan Belson wrote: Matthew Seaman wrote: Yes. root is specifically exempted from all the masquerading stuff. There's an EXPOSED_USER macro you can use in $(hostname).mc to control that. Ah, that explains it. There doesn't seem to be a way to remove exposed users, but there is a web page explaining how to stop 'root' being added as a default exposed user: http://www.grok.org.uk/docs/smroot.html Instead of doing this, I've told periodic.conf to send its output to my local account on the server, and added a .forward file to pass the e-mail to my 'real' address. Hopefully this will play nicely with sendmail's masquerading. Of course it didn't as the e-mail's sender was still 'root' :-S I ended up following the instructions from the web page above, and after initially getting caught out by the difference between 'dnl' and '#' I finally have a configuration that works. Thanks, --Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing 'From:' address of periodic scripts
Greg Larkin wrote: Jonathan Belson wrote: | Hiya | | I set up a remote box to e-mail 'periodic' output to me directly. It | has now | stopped working, and I suspect it's because the 'From:' addresses of the | status | e-mails is of the form '[EMAIL PROTECTED]' and the ISP has upped its | anti-spam | checks. | | I see /usr/sbin/periodic itself uses the 'mail' command to send the | mails, but I | couldn't see a command line option to specify a 'From:'. I guess 'mail' | uses | 'sendmail' to send e-mail; is there a simple way of forcing a 'From:' | address | via 'sendmail' config? | Hi Jon, Have a look at this: http://www.sendmail.org/m4/masquerading.html and perhaps this, too: http://www.madboa.com/geek/sendmail-genericstable/ You can rewrite [EMAIL PROTECTED] to appear as though it's coming from a real email address by using the techniques on those pages. Please post back here if you run into any trouble! OK, thanks. After playing with MASQUERADE_AS(), MASQUERADE_DOMAIN() plus a few FEATURES(), I've managed to change the 'From:' address for e-mails sent via the command line. Unfortunately, e-mails sent via the cron-ed periodic scripts still don't get through, although if I run e.g. 'periodic daily' from the command line, the mail does reach me. The only difference I can think of is that cron runs the scripts as root. Could this cause the difference? Cheers, --Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing 'From:' address of periodic scripts
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Jonathan Belson wrote: | Greg Larkin wrote: | Jonathan Belson wrote: | | Hiya | | | | I set up a remote box to e-mail 'periodic' output to me directly. It | | has now | | stopped working, and I suspect it's because the 'From:' addresses of | the | | status | | e-mails is of the form '[EMAIL PROTECTED]' and the ISP has upped its | | anti-spam | | checks. | | | | I see /usr/sbin/periodic itself uses the 'mail' command to send the | | mails, but I | | couldn't see a command line option to specify a 'From:'. I guess | 'mail' | | uses | | 'sendmail' to send e-mail; is there a simple way of forcing a 'From:' | | address | | via 'sendmail' config? | | | Hi Jon, | | Have a look at this: http://www.sendmail.org/m4/masquerading.html and | perhaps this, too: http://www.madboa.com/geek/sendmail-genericstable/ | | You can rewrite [EMAIL PROTECTED] to appear as though it's coming from a | real email address by using the techniques on those pages. | | Please post back here if you run into any trouble! | | OK, thanks. After playing with MASQUERADE_AS(), MASQUERADE_DOMAIN() | plus a few FEATURES(), I've managed to change the 'From:' address for | e-mails sent via the command line. Unfortunately, e-mails sent via the | cron-ed periodic scripts still don't get through, although if I run e.g. | 'periodic daily' from the command line, the mail does reach me. | | The only difference I can think of is that cron runs the scripts as | root. Could this cause the difference? Yes. root is specifically exempted from all the masquerading stuff. There's an EXPOSED_USER macro you can use in $(hostname).mc to control that. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. Flat 3 ~ 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate ~ Kent, CT11 9PW, UK -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREDAAYFAki2cbQACgkQ3jDkPpsZ+VbRXgCcDzrkWTG0YsLNESOGA3H0Wof9 zk8AoJmW4bdOUC07pQ10nqw+ZluKLXtn =KZr6 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing 'From:' address of periodic scripts
Matthew Seaman wrote: Jonathan Belson wrote: | | OK, thanks. After playing with MASQUERADE_AS(), MASQUERADE_DOMAIN() | plus a few FEATURES(), I've managed to change the 'From:' address for | e-mails sent via the command line. Unfortunately, e-mails sent via the | cron-ed periodic scripts still don't get through, although if I run e.g. | 'periodic daily' from the command line, the mail does reach me. | | The only difference I can think of is that cron runs the scripts as | root. Could this cause the difference? Yes. root is specifically exempted from all the masquerading stuff. There's an EXPOSED_USER macro you can use in $(hostname).mc to control that. Ah, that explains it. There doesn't seem to be a way to remove exposed users, but there is a web page explaining how to stop 'root' being added as a default exposed user: http://www.grok.org.uk/docs/smroot.html Instead of doing this, I've told periodic.conf to send its output to my local account on the server, and added a .forward file to pass the e-mail to my 'real' address. Hopefully this will play nicely with sendmail's masquerading. Cheers, --Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Changing 'From:' address of periodic scripts
Hiya I set up a remote box to e-mail 'periodic' output to me directly. It has now stopped working, and I suspect it's because the 'From:' addresses of the status e-mails is of the form '[EMAIL PROTECTED]' and the ISP has upped its anti-spam checks. I see /usr/sbin/periodic itself uses the 'mail' command to send the mails, but I couldn't see a command line option to specify a 'From:'. I guess 'mail' uses 'sendmail' to send e-mail; is there a simple way of forcing a 'From:' address via 'sendmail' config? Cheers, --Jon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing 'From:' address of periodic scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan Belson wrote: | Hiya | | I set up a remote box to e-mail 'periodic' output to me directly. It | has now | stopped working, and I suspect it's because the 'From:' addresses of the | status | e-mails is of the form '[EMAIL PROTECTED]' and the ISP has upped its | anti-spam | checks. | | I see /usr/sbin/periodic itself uses the 'mail' command to send the | mails, but I | couldn't see a command line option to specify a 'From:'. I guess 'mail' | uses | 'sendmail' to send e-mail; is there a simple way of forcing a 'From:' | address | via 'sendmail' config? | | Cheers, | | --Jon | Hi Jon, Have a look at this: http://www.sendmail.org/m4/masquerading.html and perhaps this, too: http://www.madboa.com/geek/sendmail-genericstable/ You can rewrite [EMAIL PROTECTED] to appear as though it's coming from a real email address by using the techniques on those pages. Please post back here if you run into any trouble! Best regards, Greg - -- Greg Larkin http://www.sourcehosting.net/ http://www.FreeBSD.org/ - The Power To Serve -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIoFkC0sRouByUApARAo8OAJ9zuwcF2RL5SyZa6udBc38dMlLO3wCeOlju FZhVVFU4d+aKeWtBFSnd/7Q= =B+FE -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Periodic scripts running twice
RW wrote: On Mon, 04 Aug 2008 13:21:36 -0500 CyberLeo Kitsana [EMAIL PROTECTED] wrote: Hi! For a while, I've noticed odd behavior with periodic scripts installed by certain ports (portaudit) as well as ones I've penned myself (corescan), in that they appear to be run twice in succession every time. Base system scripts, and some add-on scripts (freshclam) are run only once, even in the same periodic batch. Is there some end state the script is expected to be in to signal periodic of a successful run? (Incl: Sample email, weekly.txt) Thanks! Is this a long-standing problem? It sounds like you didn't fully complete the UPDATING instruction for the 20070519 xorg update, and /usr/local/etc/periodic is being access both directly and via the /usr/X11R6 symlink. Try adding local_periodic=/usr/local/etc/periodic to /etc/periodic.conf The box in question doesn't even have X, as it's a headless server in a colo someplace. It's been this way since I installed the periodic scripts. I have no idea what that symlink is even doing there, unless 'make distdirs distribution' creates it now. Either way, I've added the local_periodic directive to /etc/periodic.conf. We'll see what happens when periodic runs tonight. Thanks! -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[Solved] Re: Periodic scripts running twice
CyberLeo Kitsana wrote: RW wrote: On Mon, 04 Aug 2008 13:21:36 -0500 CyberLeo Kitsana [EMAIL PROTECTED] wrote: Hi! For a while, I've noticed odd behavior with periodic scripts installed by certain ports (portaudit) as well as ones I've penned myself (corescan), in that they appear to be run twice in succession every time. Base system scripts, and some add-on scripts (freshclam) are run only once, even in the same periodic batch. Is there some end state the script is expected to be in to signal periodic of a successful run? (Incl: Sample email, weekly.txt) Thanks! Is this a long-standing problem? It sounds like you didn't fully complete the UPDATING instruction for the 20070519 xorg update, and /usr/local/etc/periodic is being access both directly and via the /usr/X11R6 symlink. Try adding local_periodic=/usr/local/etc/periodic to /etc/periodic.conf The box in question doesn't even have X, as it's a headless server in a colo someplace. It's been this way since I installed the periodic scripts. I have no idea what that symlink is even doing there, unless 'make distdirs distribution' creates it now. Either way, I've added the local_periodic directive to /etc/periodic.conf. We'll see what happens when periodic runs tonight. Thanks! Looks like that took care of the problem. Thanks for the insight! Although, that does cause me to wonder why only some of the local periodic scripts would run twice, while others would run only once. Either way, problem solved. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Periodic scripts running twice
Hi!
For a while, I've noticed odd behavior with periodic scripts installed
by certain ports (portaudit) as well as ones I've penned myself
(corescan), in that they appear to be run twice in succession every time.
Base system scripts, and some add-on scripts (freshclam) are run only
once, even in the same periodic batch.
Is there some end state the script is expected to be in to signal
periodic of a successful run?
(Incl: Sample email, weekly.txt)
Thanks!
--
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net
[EMAIL PROTECTED]
Furry Peace! - http://.fur.com/peace/
Return-Path: [EMAIL PROTECTED]
X-Original-To: root
Delivered-To: [EMAIL PROTECTED]
Received: by mtumishi.cyberleo.net (Postfix, from userid 0)
id 8C49911848; Sat, 2 Aug 2008 07:15:59 -0400 (EDT)
To: [EMAIL PROTECTED]
Subject: mtumishi.cyberleo.net weekly run output
Message-Id: [EMAIL PROTECTED]
Date: Sat, 2 Aug 2008 07:15:59 -0400 (EDT)
From: [EMAIL PROTECTED] (Charlie Root)
Rebuilding locate database:
Rebuilding whatis database:
makewhatis: already visited /usr/X11R6/man
Scanning for core files in { / /tmp /usr /var }:
-rw--- 1 root wheel - 4083712 May 2 17:12 /root/php.core
-rw--- 1 root wheel - 3170304 Jan 7 2008 /tmp/gopempJVXg/php.core
-rw--- 1 cyberleo users - 49807360 Jul 12 2007
/usr/home/cyberleo/build/httpd-2.2.4/modules/metadata/.libs/perl.core
-rw--- 1 root users - 2588672 Jul 14 2007
/usr/home/cyberleo/download/lsz.core
-rw--- 1 cyberleo users - 724992 Apr 28 11:56
/usr/home/cyberleo/nc.core
-rw--- 1 cyberleo users - 696320 Apr 20 05:04
/usr/home/cyberleo/supfiles/bash.core
-rw--- 1 root wheel - 655360 Jun 30 2007
/usr/ports/distfiles/gnome2/fetch.core
-rw--- 1 root wheel - 4460544 Jan 7 2008
/usr/ports/lang/php5-extensions/php.core
Scanning for core files in { / /tmp /usr /var }:
-rw--- 1 root wheel - 4083712 May 2 17:12 /root/php.core
-rw--- 1 root wheel - 3170304 Jan 7 2008 /tmp/gopempJVXg/php.core
-rw--- 1 cyberleo users - 49807360 Jul 12 2007
/usr/home/cyberleo/build/httpd-2.2.4/modules/metadata/.libs/perl.core
-rw--- 1 root users - 2588672 Jul 14 2007
/usr/home/cyberleo/download/lsz.core
-rw--- 1 cyberleo users - 724992 Apr 28 11:56
/usr/home/cyberleo/nc.core
-rw--- 1 cyberleo users - 696320 Apr 20 05:04
/usr/home/cyberleo/supfiles/bash.core
-rw--- 1 root wheel - 655360 Jun 30 2007
/usr/ports/distfiles/gnome2/fetch.core
-rw--- 1 root wheel - 4460544 Jan 7 2008
/usr/ports/lang/php5-extensions/php.core
-- End of weekly output --
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Periodic scripts running twice
On Mon, 04 Aug 2008 13:21:36 -0500 CyberLeo Kitsana [EMAIL PROTECTED] wrote: Hi! For a while, I've noticed odd behavior with periodic scripts installed by certain ports (portaudit) as well as ones I've penned myself (corescan), in that they appear to be run twice in succession every time. Base system scripts, and some add-on scripts (freshclam) are run only once, even in the same periodic batch. Is there some end state the script is expected to be in to signal periodic of a successful run? (Incl: Sample email, weekly.txt) Thanks! Is this a long-standing problem? It sounds like you didn't fully complete the UPDATING instruction for the 20070519 xorg update, and /usr/local/etc/periodic is being access both directly and via the /usr/X11R6 symlink. Try adding local_periodic=/usr/local/etc/periodic to /etc/periodic.conf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
disable periodic scripts
Hi How can I disable those nightly/monthly/... periodic scripts? I don't need them, these days professional monitoring software such as nagios is used to monitor 200+ systems. I can't read 200 mails showing me hundreds of lines of output even if nothings happening. Am I just deleting all the /etc/periodic/* stuff or is there a switch like: turn_off_ancient_system_administration=YES ? Tnx. _ Watch “Cause Effect,” a show about real people making a real difference. Learn more. http://im.live.com/Messenger/IM/MTV/?source=text_watchcause___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disable periodic scripts
Warner Lambert wrote: Hi How can I disable those nightly/monthly/... periodic scripts? I don't need them, these days professional monitoring software such as nagios is used to monitor 200+ systems. I can't read 200 mails showing me hundreds of lines of output even if nothings happening. Am I just deleting all the /etc/periodic/* stuff or is there a switch like: turn_off_ancient_system_administration=YES ? Tnx. If you really want to disable cron, put cron_enable=NO in /etc/rc.conf -- Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disable periodic scripts
On Sun, 30 Mar 2008 at 22:26 +0100, [EMAIL PROTECTED] confabulated: Warner Lambert wrote: Hi How can I disable those nightly/monthly/... periodic scripts? I don't need them, these days professional monitoring software such as nagios is used to monitor 200+ systems. I can't read 200 mails showing me hundreds of lines of output even if nothings happening. Am I just deleting all the /etc/periodic/* stuff or is there a switch like: turn_off_ancient_system_administration=YES ? Tnx. If you really want to disable cron, put cron_enable=NO in /etc/rc.conf Or, the OP can just comment the periodic lines within: /etc/crontab That way other cron jobs will still run. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disable periodic scripts
On Sun, 30 Mar 2008 15:18:12 -0400 Warner Lambert [EMAIL PROTECTED] wrote: Hi How can I disable those nightly/monthly/... periodic scripts? I don't need them, these days professional monitoring software such as nagios is used to monitor 200+ systems. I can't read 200 mails showing me hundreds of lines of output even if nothings happening. Am I just deleting all the /etc/periodic/* stuff or is there a switch like: turn_off_ancient_system_administration=YES ? The periodic scripts do other things apart than monitoring, but if you're sure you wont need any of the system maintenance features, and wont install any packages that rely on local period scripts, you can disable them in /etc/crontab. Otherwise, you may want to look at /etc/defaults/periodic.conf for how to send the output to rotated log-files. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: periodic scripts execution order
Russell Cloran [EMAIL PROTECTED] writes: I have a question regarding the execution order of periodic scripts. In the default configuration, scripts in /etc/periodic/*/ are executed before /usr/local/etc/periodic/*/, regardless of numbering. Surely the sensible thing to do would be to execute scripts in an order based on their numbering of the script, regardless of location? A patch to /usr/sbin/periodic to make this happen would be fairly trivial ... so, I'm wondering if there is a reason that the two are run separately? The way it currently runs there is no (elegant) way (that I can find) to write a local script which updates data before the system scripts are run. This would be nice to have. Should this be filed as a bug? In my opinion, no. Just put your own scripts under /etc/periodic and be done with it. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
periodic scripts execution order
Hi, I have a question regarding the execution order of periodic scripts. In the default configuration, scripts in /etc/periodic/*/ are executed before /usr/local/etc/periodic/*/, regardless of numbering. Surely the sensible thing to do would be to execute scripts in an order based on their numbering of the script, regardless of location? A patch to /usr/sbin/periodic to make this happen would be fairly trivial ... so, I'm wondering if there is a reason that the two are run separately? The way it currently runs there is no (elegant) way (that I can find) to write a local script which updates data before the system scripts are run. This would be nice to have. Should this be filed as a bug? Thanks in advance, Russell -- echo http://russell.rucus.net/spam/| sed 's,t/.*,t,;P;s,.*//,,;s,\.,@,;' smime.p7s Description: S/MIME cryptographic signature
custom periodic scripts
How would I go about adding scripts to periodic? I particular I have a couple of scripts to fetch virus definitions and scan my system. I gathered the is a 'proper' way to do it by using /usr/local/etc/periodic but not how to do it. -- /Xian We can't solve problems by using the same kind of thinking we used when we created them. Albert Einstein ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: custom periodic scripts
How would I go about adding scripts to periodic? I particular I have a couple of scripts to fetch virus definitions and scan my system. I gathered the is a 'proper' way to do it by using /usr/local/etc/periodic but not how to do it. Just put an executable script on a tree similar to /etc/periodic, i.e. : /usr/local/etc/periodic/daily/100.chk-virus -- -jpeg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: custom periodic scripts
--On Friday, January 28, 2005 10:32:35 PM + Xian [EMAIL PROTECTED]
wrote:
How would I go about adding scripts to periodic? I particular I have a
couple of scripts to fetch virus definitions and scan my system.
I gathered the is a 'proper' way to do it by using
/usr/local/etc/periodic but not how to do it.
Write the script. Put it in /etc/periodic/{period you want}
Name it xxx.name (as in some number that isn't already used. Scripts are
run in numerical order.)
Make it executable for root.
Edit the /etc/periodic.conf file to enable it. See the man page for
details, but the syntax is period_scriptname_enable=YES
For example, write a script name foo. Make it 250.foo and put it in
/etc/periodic/daily. Chown it root:wheel and chmod it 750. Edit
/etc/periodic.conf to read daily_foo_enable=YES.
Paul Schmehl ([EMAIL PROTECTED])
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: custom periodic scripts
Xian wrote: How would I go about adding scripts to periodic? I particular I have a couple of scripts to fetch virus definitions and scan my system. I gathered the is a 'proper' way to do it by using /usr/local/etc/periodic but not how to do it. Well, you could write shell scripts and put them in the proper dirs under /usr/local/etc/periodic, but probably the Right Thing (TM) to use is cron(8). It's there for this purpose. #sudo crontab -l -- #minhourday mon weekday command # Maintenance - antivirus scanner 30 */4* * * /usr/local/bin/freshclam /dev/null 21 # Backup Script 30 3 * * * /home/admin/scripts/backup -- Just run crontab -e as the user who needs to run the jobs; your EDITOR will open, and the example above should clue you in on some things. Note that cron(8) needs full paths as it doesn't inherit an environment from you, and also that he uses /bin/sh, so commands aren't entered in tcsh fashion In this example, freshclam is run at half past the hour, every four hours; the backup script runs at 0330 daily. Since this is root's crontab, any output from the backup script is mailed to root; in the freshclam example, all output, whether error or standard output, is deleted Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
periodic scripts
Hi all, please what is your opinion and possible repair of following. I have FreeBSD 4.10-REL-p2, cvsup+make world last week. It happened few times in last half-year, that server discontinue sending reports from periodics daily. I run it manually and see ps ax, but the only checks are started are those about security. And the only report send is security report. The daily report is never created. This status will remain until the next update. There is no difference between /usr/src/etc/default/periodic.conf and /etc/default/periodic.conf. I have reated my own /etc/periodic.conf.local, but I set only daily_status_XXX etc. variables, daily_output=root. Question - what is causing this; has anybody experience with this; how to repair it without make world ? Best regards, Peter Rosa ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: periodic scripts
On Mon, Sep 20, 2004 at 09:30:05AM +0200, Peter Rosa wrote: I have FreeBSD 4.10-REL-p2, cvsup+make world last week. It happened few times in last half-year, that server discontinue sending reports from periodics daily. I run it manually and see ps ax, but the only checks are started are those about security. And the only report send is security report. The daily report is never created. This status will remain until the next update. Question - what is causing this; has anybody experience with this; how to repair it without make world ? A common cause of this sort of thing is the /var partition filling up -- if /var is full, then you can't send e-mails because you can't write the spool files in /var/spool/mqueue or /var/spool/clientmqueue -- if you're delivering to the same machine, /var/mail will be blocked as well. Other than the usual check for rubbish files: old cores, stuff cluttering up /var/tmp etc. it's a case of hunting for what is hogging the space and doing something to reduce the usage. Check /var/crash -- if you've enabled system core dumps and your system has crashed a few times, you'll find a number of rather large files in there, which you probably won't need any more. Look at eg. MySQL databases, which can grow very quickly if you turn logging on. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpNwde1fUK0m.pgp Description: PGP signature
Periodic Scripts - Configuration problem?
I recently change the hostname of my FreeBSD host to remove a hyphen from the name (i.e. skrap-node to skrapnode) Since then, all of the periodic output scripts send their mail output to [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Only the mail delivery failures make it to my inbox. Mail works fine for all users, this just affects the periodic scripts. I have tried grep'ing for the incorrect hostname in the /etc/periodic/blah... But haven't found anything. skrapnode# uname -a FreeBSD skrapnode.skrap.net 5.2-BETA FreeBSD 5.2-BETA #0: Sun Nov 23 00:01:14 CST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 skrapnode# more /etc/hosts 127.0.0.1 localhost.skrap.net localhost 192.168.1.200 skrapnode.skrap.net skrapnode 192.168.1.200 skrapnode.skrap.net. skrapnode# skrapnode# more /etc/rc.conf # -- sysinstall generated deltas -- # Sat Nov 22 10:46:24 2003 # Created: Sat Nov 22 10:46:24 2003 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. defaultrouter=192.168.1.1 hostname=skrapnode.skrap.net ifconfig_fxp0=inet 192.168.1.200 netmask 255.255.255.0 kern_securelevel_enable=NO linux_enable=YES sendmail_enable=YES sshd_enable=YES usbd_enable=YES skrapnode# Jack W. Parks IV Sr. Network Engineer ALLTEL Communications jack.w.parks-at-alltel.com Work: 501-905-5961 Cell: 501-680-3341 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Periodic Scripts - Configuration problem?
On Tue, 2003-12-02 at 11:18, [EMAIL PROTECTED] wrote: I recently change the hostname of my FreeBSD host to remove a hyphen from the name (i.e. skrap-node to skrapnode) Since then, all of the periodic output scripts send their mail output to [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Only the mail delivery failures make it to my inbox. Mail works fine for all users, this just affects the periodic scripts. Do you have anything still funky in your /etc/mail/aliases or other files that may have influence on the flow of mail? Steve I have tried grep'ing for the incorrect hostname in the /etc/periodic/blah... But haven't found anything. skrapnode# uname -a FreeBSD skrapnode.skrap.net 5.2-BETA FreeBSD 5.2-BETA #0: Sun Nov 23 00:01:14 CST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 skrapnode# more /etc/hosts 127.0.0.1 localhost.skrap.net localhost 192.168.1.200 skrapnode.skrap.net skrapnode 192.168.1.200 skrapnode.skrap.net. skrapnode# skrapnode# more /etc/rc.conf # -- sysinstall generated deltas -- # Sat Nov 22 10:46:24 2003 # Created: Sat Nov 22 10:46:24 2003 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. defaultrouter=192.168.1.1 hostname=skrapnode.skrap.net ifconfig_fxp0=inet 192.168.1.200 netmask 255.255.255.0 kern_securelevel_enable=NO linux_enable=YES sendmail_enable=YES sshd_enable=YES usbd_enable=YES skrapnode# Jack W. Parks IV Sr. Network Engineer ALLTEL Communications jack.w.parks-at-alltel.com Work: 501-905-5961 Cell: 501-680-3341 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: Re: Periodic Scripts - Configuration problem?]
[EMAIL PROTECTED] wrote: I recently change the hostname of my FreeBSD host to remove a hyphen from the name (i.e. skrap-node to skrapnode) Since then, all of the periodic output scripts send their mail output to [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Only the mail delivery failures make it to my inbox. Mail works fine for all users, this just affects the periodic scripts. I have tried grep'ing for the incorrect hostname in the /etc/periodic/blah... But haven't found anything. the easiest thing to check right now is the output of hostname. also, i *think* that the periodic scripts send mail to root (i.e., they don't add the domain), so perhaps sendmail is adding this? try: # sendmail -bv root if that is the case, check /etc/mail/sendmail.cf for the hardcoded hostname, or give sendmail a bit of -HUP (make restart in /etc/mail) hope this helps ~jon - Yesterday upon the stair I saw a man who wasn't there, he wasn't there again today, oh how i wish he'd go away Rev. Jonathan T. Sage Lighting / Set Designer Professional Web Design [HTTP://thr.msu.edu] [EMAIL PROTECTED] [PGP: www.keyserver.net] -- Yesterday upon the stair I saw a man who wasn't there, he wasn't there again today, oh how i wish he'd go away Rev. Jonathan T. Sage Lighting / Set Designer Professional Web Design [HTTP://thr.msu.edu] [EMAIL PROTECTED] [PGP: www.keyserver.net] pgp0.pgp Description: PGP signature
Periodic Scripts
Hi, (BFor reasons that I don't completely understand one of my machines has (Bstopped sending mail to root. I was used to getting the periodic output (Bmailed to me daily and now one of them has stopped. The mail does not appear (Bto be held up anywhere and is not showing up in the queue, so I am a little (Bconfused by it all. (B (BI cannot find the crontab for the user that runs these daily,weekly,monthly (Bscripts and I certainly have no recollection of changing any of these. Can (Banyone tell me where to start looking for the culprit ? (B (BThanks in advance, (B (BLukeK (B (B (B___ (B[EMAIL PROTECTED] mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
