[rt-users] need some explanation on rt.log data

[Asif Iqbal]

On Fri, Jul 9, 2010 at 2:45 PM, Kenneth Crocker <kfcrocker at lbl.gov> wrote:
> Asif,
>
> Sometimes, depending on the message, the number refers to the script being
> acted on or a user ID or a QueueID, etc. That's about all I know.

Hmm.. I went through 34000 lines of rt.log and I could not match my
user id or queue id
any where.

I am an active user resolving tickets. I also manage this box.

>
> Kenn
> LBNL
>
> On Fri, Jul 9, 2010 at 10:52 AM, Asif Iqbal <vadud3 at gmail.com> wrote:
>>
>> Hi All
>>
>> I noticed about 60% of all rt.log has a token in the following format
>>
>>  <rt-3.8.2-16815-1278696300-880.767036-185-0 at rt.example.net>
>>
>> and some of those are followed by the ticket number, transaction
>> number and Scrip number after that
>> like this
>>
>>  <rt-3.8.2-16075-1278695671-112.767031-174-0 at rt.example.net>
>> #767031/4506465 - Scrip 174 ...
>>
>> Is there a to find out what are those numbers mean?
>>
>> Obviously..
>>   767031 in that <..token> is the ticket number.
>>   rt-3.8.2 is the RT version
>>   1278695671 is probably the epoch time
>>
>> But, what are the other numbers represents ?
>>
>> --
>> Asif Iqbal
>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>>
>> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
>> Buy a copy at http://rtbook.bestpractical.com
>
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?