Re: Looking for HowTo instructions ...
On 10/5/06, Greg Thomas [EMAIL PROTECTED] wrote: On 10/4/06, Marc G. Fournier [EMAIL PROTECTED] wrote: What the software is measuring, or is trying to measure, is the number of active *BSD installations there are ... So why doesn't it do only that? Just Systems This Month: 2938 and the numbers broken down by country or continent. Greg On Thu, Oct 05, 2006 at 02:38:49AM +, Sam Fourman Jr. wrote: I for one do not mind that, BSDstats breaks out the BSD operating systems. I only wish that someone with sufficient knowledge would put the BSDstats script in the OpenBSD ports tree. because if I could install it I could add 27 OpenBSD systems. Sam Fourman Jr. I just took a look at the script, all you have to do is schedule it to be run from cron and add a line to rc.conf. I'm not sure what you'd gain by having a port. -Damian
Re: Looking for HowTo instructions ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ingo, Ingo Schwarze wrote: I doubt the project is worth the effort at all. Whatever numbers might result will be heavily biased. Of course it's biased. It's statistics of running *BSD systems. How could that possibly not biased?! BSDstats is typical bloatware that lots of OpenBSD users will hate (not all, mind you, but many more than e.g. in Linuxland). Why could bsdstats be bloatware? It's a simple shellscript, telling a remote Server Hej, I'm an OpenBSD 3.9 on i386. Gooy Bye. Bloatware is something different... bsdstats could be bloatware if it would be a huge pile of python scripts ;) It's only shell... Besides, the OpenBSD community tends to just not care about marketing. OpenBSD is about correctness, simplicity, freedom and security. Popularity is *not* among the But OpenBSD needs funding too. And popularity is one instrument of a whole lot to get funds. Keep that in mind. project goals. Most of the developers work on it because they need good code themselves - and certainly not in order to become famous. While that is true, bsdstats is not about being famous. Thus, i should expect the following attitude from typical OpenBSD users: A software for measuring popularity? How It's your attitude! boring. What, it will even run cron scripts and open network connections? No way on my machine... uuuhhh... Security Issues, hm? Yeah, sure. Now go on and disable your sshd, as it's also opening a network connection. Better unplug your ethernet cable too (and of course disable your wireless card) *SCNR* Get Real! ./Marian PS.: It's been quite a while since I was reading that much crap in one eMail. If all you said is your opinion, well, that's okay. If you tend to talk for others, and you did, than please stop that. Yes, I'm an OpenBSD user (but also a FreeBSD user and at work a Linux user too). iD8DBQFFI3n6gAq87Uq5FMsRAuFbAJ978AUuZM5GS4PH49qcqs2YrzEO+wCfW5xb KiKYTkySHkbmTeYz6xW0q+o= =9zxy -END PGP SIGNATURE-
Re: [MAYBE SPAM] Re: Looking for HowTo instructions ...
On Tue, Oct 03, 2006 at 02:51:51PM -0500, Damian Wiest wrote: | Do whatever you like. I'm simply stating my preference and providing | an alternative setup for people to consider. I don't find receiving | 200+ messages a day from cron jobs running on the network with identical | subject lines to be a particularly good setup. In this case, having | cron mail me the results of the job is not exactly what I want as you | seem to believe. | | If you can come up with a better scheme for managing emailed output from | hundreds of jobs running on hundreds of machines, then please share. | As it stands, you're merely trolling. My cronjobs do not output anything when stuff Just Works (tm). When something goes wrong, they will give output which will be sent to the admin (me). As I usually don't receive any output from my cronjobs, any cron mail I get indicates badness (except for the daily/weekly/monthly crons that get installed by default). After receiving such a mail, I will go in and fix the issue and the mails stop. I don't need my backup cron to tell me that everything went fine. That should be status quo. This default behaviour of cron works pretty well for me, actually. If I want succes-data accumulated over time, I'll make sure to do adequate logging or send that particular data somewhere by other means than the default cron mail facility. Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Looking for HowTo instructions ...
Hi Marian, Marian Hettwer wrote on Wed, Oct 04, 2006 at 11:08:11AM +0200: Ingo Schwarze wrote: I doubt the project is worth the effort at all. Whatever numbers might result will be heavily biased. To clarify: As far as i understood, BSDstats intends to measure the number of *BSD systems in production and connected to the internet. Should the ratio between existing and counted systems be different for different flavours, i would call that a bias. Thus, the main point of my comment was this: Due to cultural differences in the different *BSD communities, i seriously doubt that BSDstats can reach its stated goals, in particular while following the demonstrated design principle. Of course it's biased. It's statistics of running *BSD systems. In fact, it rather is a statistics about people running the BSDstats software. So it's more a statistics about BSDstats itself than about operating systems. How could that possibly not biased?! Well, a measurement of OS usage could be done with easily controllable biases by classical offline surveys; or you could try to use OS fingerprinting on large proxy servers (though controlling biases will be more difficult that way); ororor... Maybe such studies already exist - i did not check that. BSDstats is typical bloatware that lots of OpenBSD users will hate (not all, mind you, but many more than e.g. in Linuxland). Why could bsdstats be bloatware? [...] Well, bloatware in the *absolute* sense of software that does not add to the functionality or productivity of the server, but that does add to its complexity and maintenace effort. Some *relative* sense of software that is more complicated than it needs to be to fulfil its purpose was not intended. I explicity do not comment on BSDstats code quality. Besides, the OpenBSD community tends to just not care about marketing. OpenBSD is about correctness, simplicity, freedom and security. Popularity is *not* among the But OpenBSD needs funding too. And popularity is one instrument of a whole lot to get funds. Keep that in mind. Clearly a valid comment. But I doubt that BSDstats will be very helpful in that respect, but that's only a personal guess. To impress people, you would in particular need to be able to compare *BSD usage numbers to usage numbers of other OSs. As far as i see, BSDstats does not even try to do that. Thus, i should expect the following attitude from typical OpenBSD users: A software for measuring popularity? How It's your attitude! Admitted. boring. What, it will even run cron scripts and open network connections? No way on my machine... uuuhhh... Security Issues, hm? Well no, rather KISS (keep it stupidly simple). Don't run things unless they are needed, in particular when it comes to things like cron and daemons, yet more network daemons. On a typical server, i have a handful of networks daemons (e.g. ftp-proxy, ident, ntp, sshd on one or nfs, imap, ntp, sshd on another) so one additional is a 25% increase. I usually have exactly one cron job on a machine, so one additional is a 100% increase. Of course, KISS is *also* a matter of taste - but it is far from *only* a matter of taste. Even if it were only a matter of taste, it would be relevant as far as people's taste could bias the intended measurement. Whatever, as far as i am aware, at least during the last few weeks, nobody brought this possible flaw in the BSDstats project design to the attention of the software author(s), so i mentioned it. I have little desire to turn this into a flame or or even to discuss it much further... The BSDstats team will certainly come to their own conclusion whether the possible bias i pointed out seems dangerous to them or not.
Re: Looking for HowTo instructions ...
--On Tuesday, October 03, 2006 06:57:31 +0200 Ingo Schwarze [EMAIL PROTECTED] wrote: Marc G. Fournier wrote on Sun, Oct 01, 2006 at 10:28:34PM -0300: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I doubt the project is worth the effort at all. Whatever numbers might result will be heavily biased. BSDstats is typical bloatware that lots of OpenBSD users will hate (not all, mind you, but many more than e.g. in Linuxland). Besides, the OpenBSD community tends to just not care about marketing. OpenBSD is about correctness, simplicity, freedom and security. Popularity is *not* among the project goals. Most of the developers work on it because they need good code themselves - and certainly not in order to become famous. Thus, i should expect the following attitude from typical OpenBSD users: A software for measuring popularity? The thing is, this software isn't meant to measure popularity, at least not *between* the *BSDs ... quite frankly, I don't care that you run OpenBSD vs FreeBSD, I care that you run *BSDs vs Linux vs Windows vs ... What the software is measuring, or is trying to measure, is the number of active *BSD installations there are ... Do I expect to get 100% buy in? Hell no ... What I'm hoping for is to get high enough numbers *over time* to show places like Intel and Adaptec that by not being *truly open source* with their drivers and such, they are missing out on, what I think is, a large market ... This isn't a short term thing ... our goal is to show long term trends, and, hopefully, growth of *BSD usage in general ... to provide *reasonable* metrics for ppl like Theo to go at places like Adaptec with and point out what they missing by not being 'truly open' ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664
Re: Looking for HowTo instructions ...
On 10/4/06, Marc G. Fournier [EMAIL PROTECTED] wrote: What the software is measuring, or is trying to measure, is the number of active *BSD installations there are ... So why doesn't it do only that? Just Systems This Month: 2938 and the numbers broken down by country or continent. Greg
Re: Looking for HowTo instructions ...
I for one do not mind that, BSDstats breaks out the BSD operating systems. I only wish that someone with sufficient knowledge would put the BSDstats script in the OpenBSD ports tree. because if I could install it I could add 27 OpenBSD systems. Sam Fourman Jr. On 10/5/06, Greg Thomas [EMAIL PROTECTED] wrote: On 10/4/06, Marc G. Fournier [EMAIL PROTECTED] wrote: What the software is measuring, or is trying to measure, is the number of active *BSD installations there are ... So why doesn't it do only that? Just Systems This Month: 2938 and the numbers broken down by country or continent. Greg
Re: Looking for HowTo instructions ...
On Mon, Oct 02, 2006 at 07:54:05PM -0400, Adam wrote: Damian Wiest [EMAIL PROTECTED] wrote: Suppose your cron jobs don't emit output, which any good job shouldn't do. Huh? If you want a task to run on a schedule, and then mail you the results, then cron is exactly what you want. Any good job does what its author wants it to. If they want it to emit output, then having it be silent for no reason does not make it a good job. Adam The way I structure my jobs, no output is _ever_ mailed by the cron daemon. Instead, the job itself traps output and sends an appropriate email message, with an appropriate subject to the appropriate user. An email message with a subject line of 'Output from cron job' is useless. Messages with a subject of [SUCCESS] backup.sh or [FAILURE] backup.sh are much more useful. I can filter the messages more easily, I have more confidence in a junior admin not missing an important message and I can have success and error conditions notify different people. I get daily email messages from too many jobs running as root on too many different machines for cron's default email output to be useful. -Damian
Re: Looking for HowTo instructions ...
Damian Wiest [EMAIL PROTECTED] wrote: On Mon, Oct 02, 2006 at 07:54:05PM -0400, Adam wrote: Damian Wiest [EMAIL PROTECTED] wrote: Suppose your cron jobs don't emit output, which any good job shouldn't do. Huh? If you want a task to run on a schedule, and then mail you the results, then cron is exactly what you want. Any good job does what its author wants it to. If they want it to emit output, then having it be silent for no reason does not make it a good job. Adam The way I structure my jobs, no output is _ever_ mailed by the cron daemon. Instead, the job itself traps output and sends an appropriate email message, with an appropriate subject to the appropriate user. Good for you. But what Damian likes to do is not the definition of good. Like I said, if someone wants output mailed from cron, then making the job silent just because Damian thinks that's good is dumb. Adam
Re: [MAYBE SPAM] Re: Looking for HowTo instructions ...
On Tue, Oct 03, 2006 at 03:06:20PM -0400, Adam wrote: Damian Wiest [EMAIL PROTECTED] wrote: On Mon, Oct 02, 2006 at 07:54:05PM -0400, Adam wrote: Damian Wiest [EMAIL PROTECTED] wrote: Suppose your cron jobs don't emit output, which any good job shouldn't do. Huh? If you want a task to run on a schedule, and then mail you the results, then cron is exactly what you want. Any good job does what its author wants it to. If they want it to emit output, then having it be silent for no reason does not make it a good job. Adam The way I structure my jobs, no output is _ever_ mailed by the cron daemon. Instead, the job itself traps output and sends an appropriate email message, with an appropriate subject to the appropriate user. Good for you. But what Damian likes to do is not the definition of good. It's my definition :) Like I said, if someone wants output mailed from cron, then making the job silent just because Damian thinks that's good is dumb. Adam Do whatever you like. I'm simply stating my preference and providing an alternative setup for people to consider. I don't find receiving 200+ messages a day from cron jobs running on the network with identical subject lines to be a particularly good setup. In this case, having cron mail me the results of the job is not exactly what I want as you seem to believe. If you can come up with a better scheme for managing emailed output from hundreds of jobs running on hundreds of machines, then please share. As it stands, you're merely trolling. -Damian
Re: [MAYBE SPAM] Re: Looking for HowTo instructions ...
Damian Wiest [EMAIL PROTECTED] wrote: Do whatever you like. I'm simply stating my preference and providing an alternative setup for people to consider. I don't find receiving 200+ messages a day from cron jobs running on the network with identical subject lines to be a particularly good setup. In this case, having cron mail me the results of the job is not exactly what I want as you seem to believe. I didn't say its exactly what you want, I said its exactly what the person asking about periodic wants. You are the one making blanket statements about bad cron jobs without considering what is intended. If you can come up with a better scheme for managing emailed output from hundreds of jobs running on hundreds of machines, then please share. As it stands, you're merely trolling. I don't need to come up with any such scheme, as I don't have any such problem. I simply said that cron is ideal for running a task and then sending an email about it. This is true wether you let cron send the mail or if you do it yourself in the script. I think you need to learn what a troll is, or stop tossing it around like that. You are not the definition of good, and telling you as much is not trolling. Adam
Re: Looking for HowTo instructions ...
On Sun, Oct 01, 2006 at 11:46:48PM -0300, Marc G. Fournier wrote: http://www.openbsd.org/cgi-bin/man.cgi?query=periodicapropos=1 Perfect, now, what the man page doesnt' seem to indicate is where the best place for putting the 'config variables' ... under FreeBSD, this goes in /etc/periodic.conf ... where does OpenBSD put it? same, or /etc/rc.conf.local? it does indicate it. it says that these files are shell scripts, run by cron. so you can put whatever you normally put in a shell script in the shell script, and whatever you normally put in your cron config files in your cron config files. the page also indicates in various places if things need to be set in crontab, and so on. if there are any caveats, i'd like to know them. jmc
Re: Looking for HowTo instructions ...
2006/10/2, Marc G. Fournier [EMAIL PROTECTED]: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I Usually through ports(7). Best Martin
Re: Looking for HowTo instructions ...
On Sun, 1 Oct 2006, Jason LaRiviere wrote: $ ls -l /var/log/*.out -rw-r--r-- 1 root wheel 1693 Oct 1 01:31 /var/log/daily.out -rw-r--r-- 1 root wheel15 Oct 1 05:30 /var/log/monthly.out -rw-r--r-- 1 root wheel59 Sep 30 03:32 /var/log/weekly.out Hello everyone, can anyone tell me why this is information is (by default) 644 and not 600 or 640 for example? At least in daily log mailq cannot be run as regular user (with postfix from ports this appears to be possible too). Weekly and monthly logs doesn't seem to contain (I didn't check very thorougly) anything that normal user can't obtain, unless admin has added something to the .local scripts. -- Antti Harri
Re: Looking for HowTo instructions ...
Cross-list addresses removed. Come on, is it so difficult to post the same message (or even lightly personalized message?) three or four times so we can minimize the cross-list trash that results from people hitting group reply mindlessly? Marc G. Fournier wrote: The point of using periodic, at least under FreeBSD, is that there is a 'report' that is issued at the end of the monthly periodic run letting the admin know the status of various things on their servers ... So, for instance, it would give them a monthly reminder that the script *is* running on their machine ... sounds like it should go in the /etc/monthly.local script. Whomever gets the rest of the system reports will get that. http://www.openbsd.org/cgi-bin/man.cgi?query=monthlysektion=8 however, this does run as root, so you will probably want to make sure that is delt with properly. Still...there is no magic here, the difference between this and cron is just the wrapper scripts. Cron is Unix. This periodic thingie is apparently FreeBSD. If this is a cross-platform app, it should be Unix, not FreeBSD. Watching how bsdstats.org has been acting mostly as a random number generator for at least the last week or so has been amusing, but doesn't do much for faith in the project. It can claim to be fair, as I think it has ranked each of the major BSDs as most popular by a huge margin at least once in the last week, but I wouldn't call that meaningful. I think you need to be providing some clear, accurate, front-page explanation of how you are compiling your numbers. If you are having temporary difficulties, the responsible thing to do is to not display garbage. Otherwise, you truly are acting as nothing better than a random number generator, and one that might be interpreted as meaningful by someone in the press or management. They do things like that, you know. Nick.
Re: Looking for HowTo instructions ...
On Mon, Oct 02, 2006 at 08:21:30PM +0200, Manuel Bouyer wrote: On Mon, Oct 02, 2006 at 12:02:34AM -0300, Marc G. Fournier wrote: The point of using periodic, at least under FreeBSD, is that there is a 'report' that is issued at the end of the monthly periodic run letting the admin know the status of various things on their servers ... So, for instance, it would give them a monthly reminder that the script *is* running on their machine ... The standard output and errors of cron jobs is mailed to the owner of the cron tab. I'm not sure what periodic can do more in this area. -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] NetBSD: 26 ans d'experience feront toujours la difference -- Suppose your cron jobs don't emit output, which any good job shouldn't do. -Damian
Re: Looking for HowTo instructions ...
Damian Wiest [EMAIL PROTECTED] wrote: Suppose your cron jobs don't emit output, which any good job shouldn't do. Huh? If you want a task to run on a schedule, and then mail you the results, then cron is exactly what you want. Any good job does what its author wants it to. If they want it to emit output, then having it be silent for no reason does not make it a good job. Adam
Re: Looking for HowTo instructions ...
On Mon, Oct 02, 2006 at 12:02:34AM -0300, Marc G. Fournier wrote: The point of using periodic, at least under FreeBSD, is that there is a 'report' that is issued at the end of the monthly periodic run letting the admin know the status of various things on their servers ... So, for instance, it would give them a monthly reminder that the script *is* running on their machine ... The standard output and errors of cron jobs is mailed to the owner of the cron tab. I'm not sure what periodic can do more in this area. -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] NetBSD: 26 ans d'experience feront toujours la difference --
Re: Looking for HowTo instructions ...
Marc G. Fournier [EMAIL PROTECTED] writes: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I've put together a very rough draft for a BSDstats getting started guide, available for digestion and criticism at http://bsdly.net/~peter/bsdstat/. And yes, the bits about OpenBSD are extremely similar to the instructions at bsdstats.org for a very good reason ;) -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ First, we kill all the spammers The Usenet Bard, Twice-forwarded tales 20:11:56 delilah spamd[26905]: 146.151.48.74: disconnected after 36099 seconds
Re: Looking for HowTo instructions ...
On Mon, Oct 02, 2006 at 08:21:30PM +0200, Manuel Bouyer wrote: On Mon, Oct 02, 2006 at 12:02:34AM -0300, Marc G. Fournier wrote: The point of using periodic, at least under FreeBSD, is that there is a 'report' that is issued at the end of the monthly periodic run letting the admin know the status of various things on their servers ... So, for instance, it would give them a monthly reminder that the script *is* running on their machine ... The standard output and errors of cron jobs is mailed to the owner of the cron tab. I'm not sure what periodic can do more in this area. It just saves you from getting multiple messages. Putting a script in /etc/periodic/monthly is exactly the same as adding that script onto/into /etc/monthly.local. In fact, FreeBSD still has /etc/monthly.local, which is run by /etc/monthly/999.local. Part of the adding and removing scripts from directories is easier for the package management system than sed scripts theory, I suspect. Cheers, -- Andrew
Re: Looking for HowTo instructions ...
Marc G. Fournier wrote on Sun, Oct 01, 2006 at 10:28:34PM -0300: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I doubt the project is worth the effort at all. Whatever numbers might result will be heavily biased. BSDstats is typical bloatware that lots of OpenBSD users will hate (not all, mind you, but many more than e.g. in Linuxland). Besides, the OpenBSD community tends to just not care about marketing. OpenBSD is about correctness, simplicity, freedom and security. Popularity is *not* among the project goals. Most of the developers work on it because they need good code themselves - and certainly not in order to become famous. Thus, i should expect the following attitude from typical OpenBSD users: A software for measuring popularity? How boring. What, it will even run cron scripts and open network connections? No way on my machine...
Looking for HowTo instructions ...
Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I do not believe that either OpenBSD or NetBSD has a 'periodic' system similar to FreeBSDs, and would like to put something up on the site explaining how to install such that it runs once a month, specific to each flavors recommended method ... Thx ...
Re: Looking for HowTo instructions ...
--On Sunday, October 01, 2006 22:04:05 -0400 Jeremy Huiskamp [EMAIL PROTECTED] wrote: On 1-Oct-06, at 9:28 PM, Marc G. Fournier wrote: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I do not believe that either OpenBSD or NetBSD has a 'periodic' system similar to FreeBSDs, and would like to put something up on the site explaining how to install such that it runs once a month, specific to each flavors recommended method ... Thx ... http://www.openbsd.org/cgi-bin/man.cgi?query=periodicapropos=1 Perfect, now, what the man page doesnt' seem to indicate is where the best place for putting the 'config variables' ... under FreeBSD, this goes in /etc/periodic.conf ... where does OpenBSD put it? same, or /etc/rc.conf.local? Thx ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664
Re: Looking for HowTo instructions ...
On 1-Oct-06, at 9:28 PM, Marc G. Fournier wrote: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I do not believe that either OpenBSD or NetBSD has a 'periodic' system similar to FreeBSDs, and would like to put something up on the site explaining how to install such that it runs once a month, specific to each flavors recommended method ... Thx ... http://www.openbsd.org/cgi-bin/man.cgi?query=periodicapropos=1 Searchable, online man pages. Imagine that!
Re: Looking for HowTo instructions ...
On 10/1/06, Marc G. Fournier [EMAIL PROTECTED] wrote: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I do not believe that either OpenBSD or NetBSD has a 'periodic' system similar to FreeBSDs, and would like to put something up on the site explaining how to install such that it runs once a month, specific to each flavors recommended method ... Wouldn't cron be best suited for this task? That would seem pretty logical for running a shell script on a timed basis. It's also quite portable. I read the man page for periodic, but the usefulness of it seems quite mysterious to me. ;) From crontab(5): @monthlyRun once a month, 0 0 1 * *. (personally, I like the 0 0 1 * * method) _Matt
Re: Looking for HowTo instructions ...
The point of using periodic, at least under FreeBSD, is that there is a 'report' that is issued at the end of the monthly periodic run letting the admin know the status of various things on their servers ... So, for instance, it would give them a monthly reminder that the script *is* running on their machine ... --On Sunday, October 01, 2006 22:51:35 -0400 matthew sporleder [EMAIL PROTECTED] wrote: On 10/1/06, Marc G. Fournier [EMAIL PROTECTED] wrote: Can someone that has installed BSDstats on your server please email me instructions on *how* to install it for your flavor of BSD? I do not believe that either OpenBSD or NetBSD has a 'periodic' system similar to FreeBSDs, and would like to put something up on the site explaining how to install such that it runs once a month, specific to each flavors recommended method ... Wouldn't cron be best suited for this task? That would seem pretty logical for running a shell script on a timed basis. It's also quite portable. I read the man page for periodic, but the usefulness of it seems quite mysterious to me. ;) From crontab(5): @monthlyRun once a month, 0 0 1 * *. (personally, I like the 0 0 1 * * method) _Matt Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664
Re: Looking for HowTo instructions ...
Marc G. Fournier wrote: The point of using periodic, at least under FreeBSD, is that there is a 'report' that is issued at the end of the monthly periodic run letting the admin know the status of various things on their servers ... So, for instance, it would give them a monthly reminder that the script *is* running on their machine ... $ ls -l /var/log/*.out -rw-r--r-- 1 root wheel 1693 Oct 1 01:31 /var/log/daily.out -rw-r--r-- 1 root wheel15 Oct 1 05:30 /var/log/monthly.out -rw-r--r-- 1 root wheel59 Sep 30 03:32 /var/log/weekly.out -- jason
