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 ...

On 10/1/06, Marc G. Fournier <scrappyfreebsd.org> 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):
          monthly        Run once a month, "0 0 1 *
*".

 (personally, I like the 0 0 1 * * method)
_Matt

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 
<msporledergmail.com> wrote:

> On 10/1/06, Marc G. Fournier <scrappyfreebsd.org> 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):
>           monthly        Run 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 . scrappyhub.org                              MSN .
scrappyhub.org
Yahoo . yscrappy               Skype: hub.org        ICQ .
7615664

2006/10/2, Marc G. Fournier <scrappyfreebsd.org>:
> 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

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.          
Manuel.Bouyerlip6.fr
     NetBSD: 26 ans d'experience feront toujours la
difference
--

"Marc G. Fournier" <scrappyfreebsd.org> 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/~p
eter/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.lin
ux.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

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