![]() If there’s nothing of interest there, but you think there should be, then you’re going to need to see a bit more of the log file, and perhaps find out when it was ‘rotated’ or ‘turned over’ (i.e., the last time the system archived the install.log and created a new one). This will return a list of every item successfully installed since the new log file was created. ![]() Grep 'Installed' /private/var/log/install.log Open the Terminal.app (Utilities/Terminal.app) and copy and paste this command: Apple buries the logs deep into parts of OS X that ordinary users typically don’t reach, but fortunately, there’s numerous ways to get at your install logs, and though some of them may be unfamiliar, none of them are particularly difficult or dangerous. Typically, we’re only going to be interested in examining the most recent log file if troubleshooting new problems, but the process that I’m going to describe here can also be used to view the older logs, too. Pro Tip No.1: if you’re a Terminal whizz and you want to change how many old logs are kept or at what size the log file gets turned over, you can edit the /etc/nf file, but be sure to read the man page for newsyslog first. It then compresses and keeps the old logs, typically up to five logs prior to the current one. Secondly, the reason you may have more than one install log is that OS X creates new install logs every time the log file gets to around 1MB in size. The most recent one is simply called install.log, older ones will have a filename ending with. Firstly, chances are you’ll find more than one install log in your logs folder. I’ll tell you how to do that in a moment – in a number of ways – but first let’s just make a few notes. DetectX 2 now has a system analyser that records and displays changes to your system configuration over time.Įver wondered if a link you clicked sneakily downloaded and installed some unwanted software on your mac? Or have you suddenly found your mac behaving weirdly, a situation that is often a result of installing new software that conflicts with something else on the system, but can’t remember what you recently installed? In these sorts of scenarios, what you need to do is check your install logs. Harmless to me, but I don't want to forward it to anybody on a Windows machine, so I let the scanner(s) quarantine them.UPDATE: I’ve written a free app that pretty much supercedes what I wrote in this post. What they find, when they find anything, is usually in some email message from a Windows user. Every once in a while (every 6 months, or more) I may run DetectX Swift and/or Intego VirusBarrier Scanner to look to see if anything has crept in. I have no such software on my MBP, it stays on 24/7/365 unless I'm traveling with it and have to shut it down. They just take up cycles and don't do anything really useful. Nothing happened.įrankly, you don't need to have malwarebytes, or any antivirus software, running 24/7 on a Mac. That one is easy to stop by just shutting down the browser before you go away from it.Īs for your passwords, I don't think you need to panic. It could have been in an advert on a website or social media if the website has them changing on some timed basis. That's about all Malwarebytes can detect, as there are no true viruses for macOS at this time. ![]() ![]() I would bet that what Malwarebytes is crowing about is that it detected some email arriving that had Windows malware attached. As you noted, if you didn't run anything or go anywhere on the net, you didn't expose your machine to anything. ![]()
0 Comments
Leave a Reply. |