Closed GoogleCodeExporter closed 8 years ago
This is clearly explained in the documentation and/or by using the 'help'
command in
logKextClient.
Original comment by d235...@gmail.com
on 19 Nov 2009 at 6:20
um, actually 'help' doesn't mention anything about how to delete a log file.
It doesn't specifically tell you how to change the password either, but that
can be figured out by using the 'list' and 'set' commands.
Original comment by davidmc%...@gtempaccount.com
on 30 Nov 2010 at 4:20
i have the same problem,
the help command explains very clare how to encrypt the log file but no how to
clear the log....
Original comment by servin.e...@gmail.com
on 28 Dec 2010 at 5:28
I do not know how to delete the history but to stop logging to type set
Logging=off
to turn it on type set Logging=on
Original comment by nicotech...@gmail.com
on 29 Mar 2011 at 12:53
I do not know how to delete the history but to stop logging to type set
Logging=off
to turn it on type set Logging=on
Original comment by nicotech...@gmail.com
on 29 Mar 2011 at 12:53
I do not know how to delete the history but to stop logging to type set
Logging=off
to turn it on type set Logging=on
Original comment by nicotech...@gmail.com
on 29 Mar 2011 at 12:54
I cant delete the logfile fro the trash after I found it in the Library. I keep
on deleting it from the Library and it keeps on creating new logfiles, but when
I try to delete them from the trash it always says that its in use, so now I
have a collection of logfiles in my trash. Does anyone know how to get rid of
this?
Original comment by joirimin...@gmail.com
on 14 May 2011 at 11:50
uninstall then re-install
Original comment by NewExped...@gmail.com
on 28 Jul 2011 at 7:45
uninstall then re-install
Original comment by NewExped...@gmail.com
on 28 Jul 2011 at 7:45
Hello...
You need to type in the Terminal:
sudo rm /Library/Preferences/com.fsb.logKext
And thats it, the Log File was delete!
Original comment by tousm...@gmail.com
on 30 Aug 2012 at 5:53
tried it dosent work?
Original comment by faj3...@gmail.com
on 12 Dec 2012 at 9:54
Original issue reported on code.google.com by
sravan.s...@gmail.com
on 17 Nov 2009 at 5:25