[App_rpt-users] Time announcement

[Jared Paxton]

Ok. Thank you Doug.

On Monday, November 18, 2013, Doug Crompton wrote:

> The commands in rpt.conf are -
> [functions]
>
> 80=status,11    ; ID (local)
> 81=status,12    ; Time of Day (local)
>
> There are local and global commands for this but I suspect you only want
> or should do it locally on your radio node. You can assign anything you
> want to the left of the equal sign above as long as it does not conflict
> with other user commands. If you are not sure what you are doing leave it
> as it is.
>
> Then in the macro context you can specify what to do.
> Here I show time followed by CWID.
>
> [macro]
> ;Macro number = command string (ea command separated by space) -end with
> HASH
> 1=*81 *80#    ; play time, CWID
>
> and finally in the schedule context you specify when to do it.
>
> [schedule]
> ;dtmf_function =  m h dom mon dow  ; ala cron, star is implied
>
> 1=00 * * * *   ;run macro 1 on the hour
>
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> > From: kk4rjy at gmail.com <javascript:_e({}, 'cvml', 'kk4rjy at gmail.com');>
> > Date: Mon, 18 Nov 2013 19:05:41 -0500
> > To: app_rpt-users at ohnosec.org <javascript:_e({}, 'cvml',
> 'app_rpt-users at ohnosec.org');>
> > Subject: [App_rpt-users] Time announcement
> >
> > What is the script i can put in my schedule to have it announce the time
> hourly?
> >
> > Thanks
> >
> >
> > On Nov 18, 2013, at 12:00 PM, app_rpt-users-request at ohnosec.org wrote:
> >
> > > Send App_rpt-users mailing list submissions to
> > > app_rpt-users at ohnosec.org
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > > or, via email, send a message with subject or body 'help' to
> > > app_rpt-users-request at ohnosec.org
> > >
> > > You can reach the person managing the list at
> > > app_rpt-users-owner at ohnosec.org
> > >
> > > When replying, please edit your Subject line so it is more specific
> > > than "Re: Contents of App_rpt-users digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > > 1. Re: e2fsck (Benjamin L. Naber)
> > >
> > >
> > > ----------------------------------------------------------------------
> > >
> > > Message: 1
> > > Date: Mon, 18 Nov 2013 11:45:24 -0500
> > > From: "Benjamin L. Naber" <Benjamin at kb9lfz.com>
> > > To: "app_rpt-users at ohnosec.org" <app_rpt-users at ohnosec.org>
> > > Subject: Re: [App_rpt-users] e2fsck
> > > Message-ID: <1384793124.3179.8.camel at benjamin-hp>
> > > Content-Type: text/plain; charset="UTF-8"
> > >
> > > That's what it appears to me.
> > >
> > > A ham this morning told me the problem maybe the person making the
> > > distro images is using a windows machine, not linux, and he is making
> > > the .img files for FAT when they *should* be ext2
> > >
> > > I've been trying everything that I can find to do the filesystem check,
> > > but every embedded distro I've tried doesn't support checking DOS or
> FAT
> > > files systems.
> > >
> > > ~Benjamin, KB9LFZ
> > > allstar node 28569
> > >
> > >
> > >
> > >
> > > On Mon, 2013-11-18 at 09:37 -0600, Geoff wrote:
> > >> On 11/18/2013 07:44 AM, Benjamin L. Naber wrote:
> > >>> this is coming up when trying to boot a new install of Limey Linux
> > >>>
> > >>> last time I checked, e2fsck is for EXT2 and other Linux extensions,
> not
> > >>> FAT.
> > >>>
> > >>> Booting comes to a dead halt when the e2fsck checktime has been
> > >>> reached.
> > >>>
> > >>> Any way around this, or disable this checking when booting?
> > >>
> > >> I'm no expert on Limey Linux, but last I checked, when Linux formats
> and
> > >> prepares a drive, it is most certainly -not- in a FAT format.
> > >>
> > >> e2fsck is probably checking your drive on -every- bootup because
> there's
> > >> an issue with the drive.
> > >>
> > >> From 'man e2fsck' :
> > >>
> > >> DESCRIPTION
> > >> e2fsck is used to check a Linux second extended file system (ext2fs).
> > >> E2fsck also supports ext2 filesystems containing a journal, which are
> > >> also sometimes known as ext3
> > >> filesystems, by first applying the journal to the filesystem before
> > >> continuing with normal e2fsck processing. After the journal has been
> > >> applied, a filesystem will normally
> > >> be marked as clean. Hence, for ext3 filesystems, e2fsck will normally
> > >> run the journal and exit, unless its superblock indicates that
> further
> > >> checking is required.
> > >>
> > >> device is the device file where the filesystem is stored (e.g.
> /dev/hdc1).
> > >>
> > >> Note that in general it is not safe to run e2fsck on mounted
> > >> filesystems. The only exception is if the -n option is specified, and
> > >> -c, -
>


-- 
Sent From My Iphone 5 On AT&Ts 4G LTE Network
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20131118/1e2173d8/attachment.html>