- This topic has 3 replies, 2 voices, and was last updated May 17-1:28 am by sybok.
-
Posts
-
vance
I’m in the process of setting up antiX 26 runit for my use case. As I do that I would like to look at the authentication logs to analyze issues I’m having. Are there other log files that can help me determine authentication problems? If not, is there a way to implement the authentication log processes? It looks like there’s a difference between how systemd handles that as opposed to runit. I would assume I need to install additional packages but I would like guidance. Let me know if there is additional info needed.
Thank you!!!
Vance
sybok
The log you mentioned is definitely a good choice.
authentication logs to analyze issues I’m having
Could you describe the issues in detail?
Are they related to log in to your session or some other authentication (e.g. in a running dedicated additionally installed app such as ‘zoom’ or others)?
Also, output of ‘inxi -Fxz’ could help (you may have non-default desktop); if already posted elsewhere and not changed, please link such a post.Thanks for getting back to me @sybok. Unless I forget something, I’m going to attempt to give you the whole story. Keep in mind this procedure worked fine on version 23.2.
Using the 64bit full version of antiX 26, I install the OS on my hard drive. I don’t think I do anything out of the ordinary for the install of the OS. Once I’m operating off the hard drive, I want to join to an active directory domain & login as a domain user. The program I use to do this is called Closed in Directory (CID for short). The link directly to my discussion with the creator of this program is: https://sourceforge.net/p/c-i-d/discussion/installation/thread/a620bca252/.
I am inclined to think that CID has a bug & should be installing the packages necessary for the auth.log framework to work but that’s getting too deep for me. As a result the output of the auth.log is unavailable to help to determine what difference between 26 & 23.2 is keeping CID from getting configured correctly. I have attached the output of the command inxi -Fxz for your analysis.
Thanks for your help in this matter. I have been using antiX since version 21 & really love it because it turns my old computers into powerhouses that I can continue using daily for everything I do!sybok
The GitHub page https://cid-doc.github.io/ has section troubleshooting.
Did that help?
Since the thread you mentioned recommended using Samba, you could check ‘/var/log/samba’ (if present).Also, whenever a program misbehaves, I suggest to start it from terminal with maximal verbosity and see the output generated, e.g.
<misbehaving-program> --verbose | tee ~/MISBEHAVED_VERBOSE.txt
with the ‘tee’ utility redirecting output to a file (this may cause printing to termina with a delay “in blocks”).BTW, consider giving ‘antix-samba-manager’ package a try.
- You must be logged in to reply to this topic.