> I don't see the command line that executed merge-logs. Did it report a > "not found" error as you say it has done in the past? Show us what > happened!
What is there to show??? It doesn't output anything, it just creates the merged.xml file. As I said, I want to start a different thread for that. I have a few things I need to fix up, one thing at a time. > In regard to where the output is going, the odds are that it is in the > current directory when you ran merge-logs. One thing to look at is whether > the modification date of merged.xml (as you list above) is the moment when > you ran merge-logs. Although with your clock problems, that can't be > relied upon. I've confirmed that the system time and the hardware time are correct. This is something to do with sipx, it's writing the logs, it's not using the system time otherwise it would be correct. Here it is, the complete run. I deleted the old merged.xml file just to be 100% sure. # merge-logs # ls -la merged.xml -rw-r--r-- 1 root root 79 Jul 6 21:53 merged.xml # more merged.xml <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <sipTrace> </sipTrace> That's it, not much else to post. I need to find out what's wrong with that, in another thread would be better.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
