So ein etwas komisches thema für manche

Grund ist die diskusion im CCleaner forum: **External links are only visible to Support Staff****External links are only visible to Support Staff**

Ich frage mich wo \JDownloader*2*\logs liegen?

in %LocalAppData% oder im Installations? Was ist richtig?

Weil bei mir liegt es im Installations ordner

Laut eng support sollte er in %LocalAppData% liegen bzw auch in folgenden thema:

http://board.jdownloader.net/showthr...08147&langid=5


Was ist nun richtig bzw. woran liegt es das er im installations Ordner liegt?

[raztoki]

piriform forum thread is inaccurate

jd2 does not force install to %localappdata% %appdata (for xp) (advanced setting to change defaults), though it is our default and preferred install path. Installing to program files paths can have implications for users that do not have admin privileges.

the cfg directory should NEVER be touched by any cleanup program.

jd2install/logs/(sessionid)/files

log settings!
settings > advanced > filter: Log: or log
Log: Cleanup Logs Older Than XDays
Log: Max Log Files

purging logs shouldn't be required it should be handled all within JD and or uninstall event. Logs are also locked whilst program is running, so external programs could have permission issues. If you have to clean via 3rd party tool, advise this is done whilst JD is closed to ensure no permission issues occur.

captcha images I believe are also cleaned up automatically. though 3rd party cleanup tools shouldn't cause too much trouble.

I advise against any recursive delete rule of tmp/.

FileKey1=%LocalAppData%\JDownloader*2*\tmp|*.*|RECURSE

All libs which are extracted are deleted on close of application. We hold permanent files in this path which is our plugin cache. These files get updated/maintained by core routines. If you run cleanup program all the time and it purges tmp it can dramatically slow down JD2 start time, as plugin cache has to be recreated. It also holds update information, which is small which would be relatively safe to remove but it can be useful to determine faults in update system if you ever have any.

hope that helps, google translate kinda failed me

raztoki

thx,

but how could you change the Usersaving path?

with: GeneralSettings: ConvertRelativePaths JD Root


But for what you need old CaptchaDialogDimensions_*.json they are generated everytime you got a new Capatcha..
and JD don't delt the old one automatic.

[raztoki]

default save path and make it support relative path ? I assume you can do that with ".\download" or even "download" along with the advanced option "ConvertRelative Paths..." checked. Please note: this will download all data to JDownloader install directory as the base of relative path! This setting is for people that want to use JD on thumb drives/removable hard drives and are running on many different systems.

CaptchaDialogDimensions_*.json are used for remembering captcha location on given screen and its x and y position, which also deals with captcha scale factor as it remembers your x and y size and scale captcha image to that frame size. This is remembered for each hoster and these settings are reused. If you want to disable such a feature you can do so by advanced setting "GraphicalUserInterfaceSettings: Captcha Dialog Unique Position By Hoster"

raztoki

In my opionion its seems that they JD2 installer use the %LocalAppData%\JDownloader*2*\ as default install path... there are jd2.exe / .jar ..... for me its it a big logic error to put an whole Programm in %localappdata%
JD put every time the usersettings in %installpath%..... Its Portable... OK but wrong in localappdata.

Better would be an Programm install in %Programfiles% and usersettings to %Localappdata%
perhabs with an settings file in %installpath% that says where the userconfig are saved at %installpath% or %localappdata%.

thx

[raztoki]

Noted! As JD has always kept all installation and user data in one directory, I don't see that changing in the short term. Well not unless Appwork change there minds, but this has been brought up many times over the years, it's always been dismissed as not required and JD is 1 user 1 install type of application.