Thanks David and Fred ... I missed that setting. I've changed it and will watch it work today. I like to use rrr|Log but it's a pain to constantly be aware of stopping/starting logs or they become way to large.
By writing at the top of the file I'm interpreting that as the 'beginning' which I'm fine with. I don't like to get to crazy with logs since the unix guy has to keep it all cleaned up. I try to make his life as easy as possible so when I need something he's very responsive. And I have to add, that my need for logs is actually minimal, but it never fails there is a 'slowness' right when there are no logs. Quite frankly the 'slowness' is rarely actually a Remedy issue, or even a db issue ... I blaming the network, that's my story and I'm sticking to it! Susan .... :) On Mon, Aug 20, 2012 at 8:01 AM, David Durling <[email protected]> wrote: > ** > > Susan,**** > > ** ** > > As far as your comment about keeping logs running, maybe you know, but you > can already do that on 7.5 by setting the Maximum Log-File Size in the > Server Admin form. When looking at the files in that case, you have to > keep in mind that when the max size is reached, it starts writing over at > the top of the file. (At least that’s behavior for us - I think we have > Create Backup selected.) So you might have entries in the bottom part > with timestamps before the top part – can be confusing if one doesn’t keep > that in mind.**** > > ** ** > > David**** > > ** ** > > David Durling**** > > University of Georgia**** > > ** ** > > ** ** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Susan Palmer > *Sent:* Friday, August 17, 2012 6:44 PM > *To:* [email protected] > > *Subject:* Re: ARS generational logging**** > > ** ** > > ** **** > > That's more clear to me now. We're still at 7.5 so I guess we'll look at > the next version that comes out for an upgrade hopefully next year.**** > > **** > > Thanks for the info Andrew and Ravi !**** > > **** > > Susan**** > > On Fri, Aug 17, 2012 at 5:38 PM, Goodall, Andrew C <[email protected]> wrote: > **** > > ** **** > > It is going to help so much in working with support. Can’t tell you how > many times a log has been unworkable or useless because it has rolled over > itself due to the fixed size “readable” limit, even 0 limit will stop at > 2gb – not that is readable/manageable anyway**** > > Max-Log-History: 3 **** > > Sql.log <- current log**** > > Sql.001.log ß oldest generation**** > > Sql.002.log**** > > Sql.003.log ß latest generation /rolled log**** > > **** > > **** > > Regards,**** > > **** > > *Andrew C. Goodall***** > > Software Engineer**** > > Development Services**** > > [email protected]**** > > *jcpenney***** > > 6501 Legacy Drive**** > > Plano, TX 75024**** > > jcp.com**** > > **** > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Susan Palmer > *Sent:* Friday, August 17, 2012 5:21 PM > *To:* [email protected]**** > > > *Subject:* Re: ARS generational logging**** > > **** > > ** **** > > Hi Andrew,**** > > **** > > Not sure what 'generational' logging is. Are you referring to a rolling > log, where you could set a max and then oldest entries drop off when the > max size is reached to make room for new entries? That would be great to > have some logs continually running for those unexpected times when you'd > like to look at something that happened but the logs weren't on.**** > > **** > > Regards,**** > > Susan**** > > On Fri, Aug 17, 2012 at 10:16 AM, Goodall, Andrew C <[email protected]> > wrote:**** > > ** **** > > I’ve been wanting generational logging in ARS for a long time.**** > > I just learned that is now available with a new ar.cg parameter > Max-Log-History**** > > **** > > I don’t know when this was implemented, maybe it was with 7.6.x but I wish > BMC would have advertised this to admins or made this accessible on the > Server Information Tab.**** > > e.g. Max-Log-History: 20 **** > > **** > > Regards,**** > > **** > > *Andrew C. Goodall***** > > Software Engineer**** > > Development Services**** > > [email protected]**** > > *jcpenney***** > > 6501 Legacy Drive**** > > Plano, TX 75024**** > > jcp.com**** > > **** > > > The information transmitted is intended only for the person or entity to > which it is addressed and > may contain confidential and/or privileged material. If the reader of this > message is not the intended > recipient, you are hereby notified that your access is unauthorized, and > any review, dissemination, > distribution or copying of this message including any attachments is > strictly prohibited. If you are not > the intended recipient, please contact the sender and delete the material > from any computer.**** > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_**** > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_**** > > > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
