Pyrenamer - a new problem

[rikona]

Friday, March 21, 2014, 1:08:13 AM, Patrick wrote:

> On 2014-03-21 05:24, rikona wrote:
>> Hello rikona,
>>
>> Thursday, March 20, 2014, 1:59:39 PM, rikona wrote:
>>
>>> When I ran 'locate pyrenamer', there were 100 or more listings.
>>
>> How can I get a listing of the dates of all these files? Might
>> help to see where the problem is...
>>
>> Thanks,
>>
>> --
>>
>>  rikona

>  From a command line:

> find / -name pyrenamer -print 2> /dev/null

> ^will find all files named pyrenamer that a normal user has access to
> Use with sudo if you want to find *all* of them on the entire system.

This will only find files whose name is pyrenamer - locate will find
files where pyrenamer is in any part of the filename, which is what I
want. What I really want is the date of the file. The idea is to try
and identify files where pyrenamer is writing information. The problem
may be that some of that written information might be causing the
problem, and seeing the dates might help to identify those files. I
could not figure out a way to get locate give me the file dates, and
find does not get all the files I'd like to look at.

> which pyrenamer

> ^will show you which pyrenamer is the first candidate to be executed if
> you type it from a command line

Thanks for the tip. I didn't know that. It shows it is in the bin
directory, which is what I expected.

> Not sure if this is the easiest route to go though... it may be
> easier to uninstall and then reinstall the package?

I did that - nothing changed, even using purge.

Thanks for the info...

-- 

 rikona