On Wed, Mar 7, 2012 at 1:22 PM, < [email protected]> wrote:
> Send Rivendell-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > or, via email, send a message with subject or body 'help' to > [email protected] Hi Wayne, thanks for the help. I installed using the debs. I'm on Ubuntu 10.04 LTS I'm not in studio at moment but will check later if theres anything in those directories. I thinkk something is missing from the package? > Message: 5 > Date: Wed, 07 Mar 2012 12:24:36 -0000 > From: "Wayne Merricks" <[email protected]> > Subject: Re: [RDD] Library problem after upgrade (al davis) > To: "User discussion about the Rivendell Radio Automation System" > <[email protected]> > Message-ID: <op.wasvfaszkhi5ns@ukpcl032> > Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes > > As part of the source install you have to copy <source > dir>/conf/rd-bin.conf to /etc/apache2/conf.d/ then restart apache2. > > Did you install this manually or use the rpms/debs? Also what distro are > you using as you'll need different --libexec flags on the configure > command (or just manually edit the conf file to match afterwards). > > On Tue, 06 Mar 2012 21:29:00 -0000, John Gough <[email protected]> > wrote: > > > I tried the solution below and no joy. I still get error - unable to > > create > > file. > > > > Also there doesn't seem to be any files in > > > > - etc/apache2/conf.d/rd-bin.conf > > or > > -/etc/rivendell/apache.conf > > > > Obviously there is something up my apache install? Can anyone advise? > > > > Thanks folks > > John > > > > > >> That's the clue I needed. > >> > >> There is a file left over from the old version that needs to be > >> removed. > >> > >> The file to remove is: > >> /etc/apache2/conf.d/rd-bin.conf > >> > >> Then restart apache with the command: > >> /etc/init.d/apache2 restart > >> > >> It has been replaced by: > >> /etc/rivendell/apache.conf > >> and a symlink to it: > >> /etc/apache2/conf.d/rivendell > >> > >> The existence of the old one blocks the new one. > >> > >> > >> al. > > ####################### > Scanned by MailMarshal > ####################### > > ############ > > Attention: > > The information contained in this message is confidential and intended > for the addressee(s) only. If you have received this message in error > or there are any problems, please notify the originator immediately. > The unauthorised use, disclosure, copying or alteration of this message > is strictly forbidden. Christian Vision or any of its subsidiaries will > not be liable for direct, special, indirect or consequential damages > arising from alteration of the contents of this message by a third party > or as a result of any virus being passed on. Please note that we reserve > the right to monitor and read any e-mails sent or received by the > company under the Telecommunications (Lawful Business Practice) > (Interception of Communications) Regulation 2000. Christian Vision is > registered in England as a limited company 2842414 and as a charity > 1031031 > > ############ > > > ------------------------------ > > Message: 6 > Date: Wed, 07 Mar 2012 07:33:38 -0500 (EST) > From: Todd Baker <[email protected]> > Subject: Re: [RDD] RDLogedit and Multiple Copies of a Log > To: User discussion about the Rivendell Radio Automation System > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > Dear Rob, > > Dont use the C word... ;) > > > Yeah, there would need to be some way that the admin priviledged user(s) > could unlock/override > the locked/open log. In the situation where no concurrent opens can exist > this would be neccessary, > and even if continously warned that could make the message something that > people just ignored... > > I think that finding an open log could be some sort of flag for this log > being open by session (pid) > number blah at a datetime with a version number, or some other system to > track them. > > I would suggest also that the option should exist that your RDLOGEDIT > works as it does now with NO > Concurrent edit checking, should someone simply not care... > > > Thanks Fred et. al for the great ideas. > > Todd Baker > > ----- Original Message ----- > From: "Rob Landry" <[email protected]> > To: "User discussion about the Rivendell Radio Automation System" < > [email protected]> > Sent: Wednesday, March 7, 2012 7:04:41 AM > Subject: Re: [RDD] RDLogedit and Multiple Copies of a Log > > > > On Tue, 6 Mar 2012, Fred Gleason wrote: > > > 1) Strict -- Don't allow concurrent editing of logs at all. > > > 2) Permissive -- Warn the user when about to open a log that is already > > open elsewhere, but allow them to override the warning. > > How can one tell that a log is open? > > What happens if someone has a log open when rdlogedit (or his or her > computer) crashes? > > > Rob > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > ------------------------------ > > Message: 7 > Date: Wed, 7 Mar 2012 08:22:11 -0500 > From: Fred Gleason <[email protected]> > Subject: Re: [RDD] RDLogedit and Multiple Copies of a Log > To: User discussion about the Rivendell Radio Automation System > <[email protected]> > Cc: User discussion about the Rivendell Radio Automation System > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > On Mar 7, 2012, at 07:04 41, Rob Landry wrote: > > > How can one tell that a log is open? > > Set a lock in the DB -- basically, a table that enumerates which logs are > open where and by whom. > > > > What happens if someone has a log open when rdlogedit (or his or her > > computer) crashes? > > Any time a system wants to open a log that appears in the lock table, it > asks the system holding the lock if that lock is still valid. If the reply > indicates that it's not (or we get no reply at all), then conclude that the > lock is stale and clear it, replacing it with our own. > > This is where the posited 'inter-host communication infrastructure' comes > in. > > Cheers! > > > |-------------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |-------------------------------------------------------------------------| > | Do not try to think outside of the box. That's impossible. Instead, | > | realise the truth. There is no box. | > | --Quoted by "larsmjoh" on GrokLaw.net | > |-------------------------------------------------------------------------| > > > > ------------------------------ > > Message: 8 > Date: Wed, 7 Mar 2012 08:22:11 -0500 > From: Fred Gleason <[email protected]> > Subject: Re: [RDD] RDLogedit and Multiple Copies of a Log > To: User discussion about the Rivendell Radio Automation System > <[email protected]> > Cc: User discussion about the Rivendell Radio Automation System > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > On Mar 7, 2012, at 07:04 41, Rob Landry wrote: > > > How can one tell that a log is open? > > Set a lock in the DB -- basically, a table that enumerates which logs are > open where and by whom. > > > > What happens if someone has a log open when rdlogedit (or his or her > > computer) crashes? > > Any time a system wants to open a log that appears in the lock table, it > asks the system holding the lock if that lock is still valid. If the reply > indicates that it's not (or we get no reply at all), then conclude that the > lock is stale and clear it, replacing it with our own. > > This is where the posited 'inter-host communication infrastructure' comes > in. > > Cheers! > > > |-------------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |-------------------------------------------------------------------------| > | Do not try to think outside of the box. That's impossible. Instead, | > | realise the truth. There is no box. | > | --Quoted by "larsmjoh" on GrokLaw.net | > |-------------------------------------------------------------------------| > > > > ------------------------------ > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > End of Rivendell-dev Digest, Vol 39, Issue 12 > ********************************************* >
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
