I see these types of messages in the xsession log:
Launched ok, pid = 5906 Launched ok, pid = 5930 Launched ok, pid = 5972 Launched ok, pid = 6014
The process IDs are momentary. They are not in the ps list.
At one point I traced the messages to the KControl/Appearances/Style dialog box. I was testing the toolbar grabber handles when I first noticed the messages. Every time I selected the Apply button, one of these messages appeared in the .xsession-errors log.
However, I see the messages without accessing KControl too. The messages seem harmless, but most people do not like mystery messages in their xsession logs. Would be nice if, like we did with the startkde script, the messages provided a prefix or other clue as to exactly what launched a process.
Darrell
I see these types of messages in the xsession log:
Launched ok, pid = 5906 Launched ok, pid = 5930 Launched ok, pid = 5972 Launched ok, pid = 6014
The process IDs are momentary. They are not in the ps list.
At one point I traced the messages to the KControl/Appearances/Style dialog box. I was testing the toolbar grabber handles when I first noticed the messages. Every time I selected the Apply button, one of these messages appeared in the .xsession-errors log.
However, I see the messages without accessing KControl too. The messages seem harmless, but most people do not like mystery messages in their xsession logs. Would be nice if, like we did with the startkde script, the messages provided a prefix or other clue as to exactly what launched a process.
Darrell
Fixed in revision 1177725. They now have a [trinity kinit] prefix.
Tim
Launched ok, pid = 5906 Launched ok, pid = 5930 Launched ok, pid = 5972 Launched ok, pid = 6014
Fixed in revision 1177725. They now have a [trinity kinit] prefix.
Okay, that sounds like the messages are no longer mystery messages. :) Do the new modified messages provide any details about what is being launched or why?
Launched ok, pid = 5906 Launched ok, pid = 5930 Launched ok, pid = 5972 Launched ok, pid = 6014
Fixed in revision 1177725. They now have a [trinity kinit] prefix.
Okay, that sounds like the messages are no longer mystery messages. :) Do the new modified messages provide any details about what is being launched or why?
No; I don't think it would be easy to add that either. KInit launches almost everything in Trinity, so you could be seeing background processes or desktop applications being launched. I was tempted to disable the message entirely; thoughts?
Tim
No; I don't think it would be easy to add that either. KInit launches almost everything in Trinity, so you could be seeing background processes or desktop applications being launched. I was tempted to disable the message entirely; thoughts?
What value do the messages provide? I can see sending stderr messages, but the stdout messages only clutter the log.
I never saw such messages with 3.5.10. Is this something new in Trinity?
If there is no way to separate stdout and stderr messages then I'd rather see none at all.
Just my one vote.
No; I don't think it would be easy to add that either. KInit launches almost everything in Trinity, so you could be seeing background processes or desktop applications being launched. I was tempted to disable the message entirely; thoughts?
What value do the messages provide? I can see sending stderr messages, but the stdout messages only clutter the log.
I never saw such messages with 3.5.10. Is this something new in Trinity?
If there is no way to separate stdout and stderr messages then I'd rather see none at all.
Just my one vote.
The more I think about it, the more I don't like those messages.
Disabled in SVN revision 1177752.
Tim
-
Darrell Anderson -
Timothy Pearson