I was browsing through KControl and later saw the following messages in the xsession-errors log:
Load smb config files from /dev/null Loaded services file OK. Server role: ROLE_STANDALONE
I think the messages should be prefixed with something like [kcontrol] so users know what was accessing the samba configuration files.
As a general guideline, I believe any stdout or stderr message Trinity generates in this manner should contain some clue about what generated the message. In these days of script kiddies and malicious users, a simple prefix like that will quiet fears.
Darrell
I was browsing through KControl and later saw the following messages in the xsession-errors log:
Load smb config files from /dev/null Loaded services file OK. Server role: ROLE_STANDALONE
I think the messages should be prefixed with something like [kcontrol] so users know what was accessing the samba configuration files.
As a general guideline, I believe any stdout or stderr message Trinity generates in this manner should contain some clue about what generated the message. In these days of script kiddies and malicious users, a simple prefix like that will quiet fears.
I fully agree. However, after some thorough searching, it appears that the Samba messages are all being generated from libsmb, a third party library used for Samba integration that is not part of Trinity. I don't know of any way to silence the messages; perhaps a bug should be reported to libsmb?
Tim
Load smb config files from /dev/null Loaded services file OK. Server role: ROLE_STANDALONE
I fully agree. However, after some thorough searching, it appears that the Samba messages are all being generated from libsmb, a third party library used for Samba integration that is not part of Trinity. I don't know of any way to silence the messages; perhaps a bug should be reported to libsmb?
Hmm. Yup, my bad! I just searched the samba source code. Looks like the first two messages are from testparm.c. The last message could be from a number of places. All three messages print to stdout when running the testparm command.
How often are users going to access that KControl module? Seldom.
Okay. Never mind!