Re: [RDD] [Off Topic] Serial Port logger?
cat serialport >> logfile is good in theory. You'll run into the problem of getting the serial port set up with the right config. The historical unix tool for that is stty, but it is somewhat painful. Maybe someone else knows another more modern tool. With stty you (used to) do things which look unnatural, like stty -a < /dev/ttyS0 to get the serial settings. The newfangled way is stty -F /dev/ttyS0 If you do get it set up so that it works you can save them into a file with 'stty -g' and blast that file at stty on system startup and then you are good to go. If it were me, and since I'm used to it, I would use stty to set the port and then write a perl script to read from it and write to the log and then I could timestamp and do other stuff if that is desired. I could shoot you a shample of that kind of thing if desired. Chris On 1/10/2014 2:24 PM, Alan Smith wrote: > WOW! Its THAT easy??? (okay, I say that now until I get into trying it!). > > Sorry, I'm a windows guy...make that "former windows guy". Windows does NOT > like other programs messing with files while they are in use. > > If I understand it, I can use cat to create the initial log file, while > logrotate will automatically empty the contents of that file into a new file > daily using the current date as the filename, and even email it, and delete > the old ones. > > SWEET! > > -Alan > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] [Off Topic] Serial Port logger?
I think so. If you use the "copytruncate" option of logrotate, it will copy the current log to an archived log file and clear out the current log. I just confirmed that doing cat >> logfile will continue to append to logfile even after truncation. On Fri, Jan 10, 2014 at 12:24 PM, Alan Smith wrote: > WOW! Its THAT easy??? (okay, I say that now until I get into trying it!). > > Sorry, I'm a windows guy...make that "former windows guy". Windows does > NOT like other programs messing with files while they are in use. > > If I understand it, I can use cat to create the initial log file, while > logrotate will automatically empty the contents of that file into a new > file daily using the current date as the filename, and even email it, and > delete the old ones. > > SWEET! > > -Alan > > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] [Off Topic] Serial Port logger?
WOW! Its THAT easy??? (okay, I say that now until I get into trying it!). Sorry, I'm a windows guy...make that "former windows guy". Windows does NOT like other programs messing with files while they are in use. If I understand it, I can use cat to create the initial log file, while logrotate will automatically empty the contents of that file into a new file daily using the current date as the filename, and even email it, and delete the old ones. SWEET! -Alan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] [Off Topic] Serial Port logger?
logrotate is your friend. From the man pages: logrotate is designed to ease administration of systems that generate large numbers of log files. It allows automatic rotation, compression, removal, and mailing of log files. Each log file may be handled daily, weekly, monthly, or when it grows too large. Normally, logrotate is run as a daily cron job. from what I remember you add your log file to the logrotate config and it rotates/emails/compresses/whatever on the schedule you specify. Regards, Wayne Merricks The Voice Asia On 10/01/14 19:34, Alan Smith wrote: I'll research it, but I forgot a little detail: Serial Logger service (for windows) rotates the files on a schedule that I specify: Such as daily (what I use). At midnight it closes out the day's file, and creates a new one. The filename of each file is the date. EASMON works similarly, but I think its rotation is fixed to a weekly bases. IMHO that is too long-if you have a RWT on Tuesday, but power fails on Thursday, you've lost the log. We have UPS systems, but I still prefer daily rotations. -Alan On 1/10/2014 1:28 PM, Karl Koscher wrote: Would something as simple as this work? cat /dev/ttySx >> easlog.txt ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] [Off Topic] Serial Port logger?
I'll research it, but I forgot a little detail: Serial Logger service (for windows) rotates the files on a schedule that I specify: Such as daily (what I use). At midnight it closes out the day's file, and creates a new one. The filename of each file is the date. EASMON works similarly, but I think its rotation is fixed to a weekly bases. IMHO that is too long-if you have a RWT on Tuesday, but power fails on Thursday, you've lost the log. We have UPS systems, but I still prefer daily rotations. -Alan On 1/10/2014 1:28 PM, Karl Koscher wrote: Would something as simple as this work? cat /dev/ttySx >> easlog.txt ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] [Off Topic] Serial Port logger?
Would something as simple as this work? cat /dev/ttySx >> easlog.txt On Fri, Jan 10, 2014 at 11:24 AM, Alan Smith wrote: > Does anyone here use linux systems to also log EAS events to text file, > and if so, what package do you recommend? > > A little more detail: > > The group I work for has a fair amount of unattended stations with nothing > more than an automation system at a transmitter site and an internet > connection for remote access. > > Currently, we usually have two systems at each site-one is our DOS based > automation, the other a windows machine that acts as a "gateway" so that we > can remote access the DOS machine. Also, the windows machine logs our EAS > events as well. I am familiar with two separate Windows loggers, once > called "serial logger service" [original website down] which I greatly > prefer, but also "EASMON". > > I would like to kill 2 birds with one stone if I can and also have our > Rivendell log EAS events if its possible at these unattended sites. These > particular stations are nothing more thank jukeboxes, so the systems aren't > stressed at all. I am researching and found a few solutions, but I figure > its best to ask the experts rather than reinvent the wheel. > > Thanks! > > -Alan > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] [Off Topic] Serial Port logger?
Does anyone here use linux systems to also log EAS events to text file, and if so, what package do you recommend? A little more detail: The group I work for has a fair amount of unattended stations with nothing more than an automation system at a transmitter site and an internet connection for remote access. Currently, we usually have two systems at each site-one is our DOS based automation, the other a windows machine that acts as a "gateway" so that we can remote access the DOS machine. Also, the windows machine logs our EAS events as well. I am familiar with two separate Windows loggers, once called "serial logger service" [original website down] which I greatly prefer, but also "EASMON". I would like to kill 2 birds with one stone if I can and also have our Rivendell log EAS events if its possible at these unattended sites. These particular stations are nothing more thank jukeboxes, so the systems aren't stressed at all. I am researching and found a few solutions, but I figure its best to ask the experts rather than reinvent the wheel. Thanks! -Alan ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Feature requests
Hello Fred, Any visibility on such an option ? That would be sooo cool ! Hoggins! Le 29/03/2013 22:55, Fred Gleason a écrit : > On Mar 28, 2013, at 10:48 21, Hoggins! wrote: > >> > Seriously, I'm thinking of an override feature, not a button I've >> > alwaysused, and previously discussed as time consuming. >> > Say that, in my case, I have a hundred of cuts in that cart. A single >> > "everred" button on the cart would be better than "clear all" on each cut. > I can see the sense of this. An 'ignore this cut until further notice' > setting. While zeroing out the dayparting does have the same effect, it also > means having remember what the dayparting is supposed to be and put it all > back in again when the cut gets turned back on. Cumbersome and error prone... > > Cheers! ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev