Hi Folks
The title says it all, whilst debugging (and therefore logging sublime commands etc) I noticed that sublime is reloading:/var/log/auth.log and I wondered why ?
Is this normal behaviour, what’s it for? If it is all normal I can get that off my list of weird things that are happening 
Thanks for your time.
At least on my system that file can only be written by the syslog. Is there a specific situation where you observed ST accessing this file?
ST does use pkexec or gksudo when saving a file requires root, which would end up being logged. Though that’s done through a child process.
Yes, from the output of the console, is it called that ? (sorry haven’t talked about these sublime things for a while so not sure of the correct terminology, when you set all the ST3 logging commands to True and get their output)
There’s a window/text box at the bottom of sublime that outputs things like:
(And this is the output copy and pasted or some of it)
reloading /var/log/auth.log
reloading .bash_history
reloading sublime-text-3/Packages/User/Default (Linux).sublime-keymap
key evt: shift+alt+l
command: run_macro_file {"file": "res://Packages/User/selectJustTextNoNLineOrTabs.sublime-macro"}
key evt: shift+alt+w
key evt: shift+alt+o
command: open_directory_under_cursor {"workspace": 3}
(I redacted some output, so as not to give away $HOME etc)
I’m trying to find out what’s what, so I was hoping you folks could tell me the context. If it’s not something that sublime does, then it’s probably something I’ve done, if it is a usual function of sublime, then maybe I can disregard it in my debugging…
That "reloading /var/log/auth.log" gets logged when a file opened in Sublime Text has changed on disk and ST reloads it. So the reason ST is reading from /var/log/auth.log is because the user has opened that file.
Thank you (of course)
I didn’t realise I had it open (buried away in many open tabs). Gosh 
Well at least I know it’s not Sublime and the weirdness that’s currently happening is down to me…all I’ve got to do now is work out what the **** I’ve done !
Thanks again
Just for completion, the weird behaviour (which I deduced) was a (linux) script I have running at start up (which makes sure all my apps are running in the correct workspace). It ran every time I executed a certain command within Sublime. (I’m not sure why).
Do to previous mistakes I’ve made some scripts are executable by all (ugo). The cure was to make the startup script only executable by me (ie u). That seems to have cured the issue.
(I’m guessing because the script is open in Sublime it runs, but then it only runs when a certain command is run, maybe because that command calls os.system. No idea!)
PS Famous last words: It all seems to be working fine now, thanks again