Log me in log in

Last edited: Mar 4, 2024 #1,152 If I have it in autopilot, which of the modes work together with the rules section?I mean if I build a rule to auto allow something, with which settings this rule is effective. The help balloon for the autopilot modes doesn't help to understand this, in fact I think the explanations are contradictory #1,153 Just to confirm that automatic whitelist cleanup isn't working for me: today my PC has been ON for more than two hours, I've checked now the whitelist and the same rule is still there. Cyberlock whitelist (2).jpg 335.8 KB · Views: 88 Azazel #1,154 Just to confirm that automatic whitelist cleanup isn't working for me: today my PC has been ON for more than two hours, I've checked now the whitelist and the same rule is still there. Same with me. danb From VoodooShield #1,155 That is odd, please look for the following log entry in your developer log, located here: C:\ProgramData\CyberLock\DeveloperLog.logCleanup Whitelist: (and date / time)Please let me know if your developer log contains entries like this, and please confirm that it is firing every hour. #1,156 That is odd, please look for the following log entry in your developer log, located here: C:\ProgramData\CyberLock\DeveloperLog.logCleanup Whitelist: (and date / time)Please let me know if your developer log contains entries like this, and please confirm that it is firing every hour. I've just checked mine. The log goes back to Sep 2023 and no cleanup whitelist entry is found. #1,157 Please let me know if your developer log contains entries like this, and please confirm that it is firing every hour. Yep, C:\ProgramData\CyberLock\DeveloperLog.log contains multiple entries firing every hour but for some reason that command never worked for me.The first entry is [12-20-2023 13:17:15] [INFO ] - Cleanup Whitelist: 12/20/2023 1:17:15 PMThe most recent entry is [03-04-2024 12:05:47] [INFO ] - Cleanup Whitelist: 3/4/2024 12:05:47 PMAlso I've checked now the whitelist and the rule I mentioned in my previous post is still there. #1,158 I looked for “cleanup” in my log and didn’t find anything. #1,159 That is odd, please look for the following log entry in your developer log, located here: C:\ProgramData\CyberLock\DeveloperLog.logCleanup Whitelist: (and date / time)Please let me know if your developer log contains entries like this, and please confirm that it is firing every hour. just searched my developerlog.log and I'm not seeing Cleanup Whitelist. running 7.70. Is

Left side of the interface.Under the “Select Items to Clean” section, check the box next to “Log Files” to select all log files for cleaning.Cleaning Application Logs using StacerClick on the “Scan” button at the bottom of the window. Stacer will then scan your system for the selected log files and display the total size of the files to be cleared. You can use “Select all” or clear only the logs you need.Selecting logs to be cleanedAfter the scan is complete, click on the “Clean” button to clear the selected log files. Stacer will remove the files and display a summary of the cleaned items.And that’s it! You’ve successfully cleared your log files using Stacer. This modern and visually appealing tool provides an intuitive and easy-to-use approach to log file management, making it a great option for those who prefer a graphical interface over the command line.My personal take on log managementI believe that each system administrator should have their unique approach to log management. Personally, I prefer combining manual and automated methods, as they complement each other well. I use manual methods for one-off log file clearings, while logrotate takes care of regular maintenance.Although some may argue that automation should be the default, I find value in occasionally taking a hands-on approach. This not only helps me stay familiar with the command line, but also allows me to keep an eye on the log files’ content, helping me stay informed about any potential issues.Additionally, I’m a strong advocate for log monitoring and analysis tools, such as Logwatch or Graylog. These tools help me keep track of important system events and alerts, which is critical for maintaining a healthy and secure system.When it comes to log management, my personal motto is “Stay proactive, stay informed.” By regularly clearing and monitoring log files, I can prevent disk space issues, quickly detect any anomalies, and ensure that my Linux systems run like a well-oiled machine.ConclusionIn this post, we’ve discussed the importance of log management and explored two of my favorite techniques for clearing system log files in Linux: manual emptying and logrotate. As a seasoned sysadmin, I believe that a combination of manual and automated methods, coupled with a proactive approach to log monitoring, is essential for maintaining efficient and secure Linux systems.Feel free to try out these methods, experiment with different tools, and develop your own personal preferences for log management. After all, every sysadmin’s journey is unique, and finding what works best for you is key to mastering the art of Linux system administration.

Problem to open log files Problem to open log files Hello everyone,I am really new at using MoTeC and I have a problem that I don't understand. I installed MoTeC i2 Pro on my laptop and when I create a new project and try to open a log file, it always tells me "There is not log file in this folder" even when there are some in the folder.I uninstalled and re-installed MoTeC but it still doesn't work. Could someone help me with this ?Thank you very much.Regards,Sandrine. 100drine Posts: 3Joined: Thu Dec 11, 2008 3:06 am Re: Problem to open log files by RossB on Fri Dec 12, 2008 9:24 am Hello Sandrine,You need to use the folder "tree" on the left to select the folder which contains the data you want to look at. By default yuor logging will be saved to the folder: C:/motec/logged data. You will only be able to open "Pro Logging" files with i2 Pro, if you do not have Pro Logging you will need to use i2 Standard. RossB Posts: 474Joined: Thu May 01, 2008 2:57 pm Re: Problem to open log files by 100drine on Sat Dec 13, 2008 5:59 am Hello again,thank you for your answer but the thing is that I have log files from the game rFactor and I am not able to open them. I have i2 Standard.I do :- "Open Log File"- I select the folder in which are my log files in "tree" folder on the left=> but the software tells me "There are no log files in this folder".I don't understand why it is not working properly. Do you have an idea of what I could do to stop that problem and be able to open my files ?Thank you.Regards,Sandrine 100drine Posts: 3Joined: Thu Dec 11, 2008 3:06 am Re: Problem to open log files by Merlin on Sat Dec 13, 2008 9:04 am you will not be able to open log files from a game...this is a copy write violationONLY log files created by a MoTeC device ...ecu ,dash acl..can be usedJohn P Merlin Posts: 56Joined: Thu Jul 10, 2008 12:47 pm Re: Problem to open log files by 100drine on Mon Dec 15, 2008 3:48 am Thank you for telling me, I had no idea it was a copy write violation.Sandrine 100drine Posts: 3Joined: Thu Dec 11, 2008 3:06 am Re: Problem to