I'm using boinc-client version 5.8.1-2build1~feisty-fawn on Ubuntu 7.04. No stderr.txt file exists in the slots folder under the boinc-client directory and hence i'm unable to get stderr outputs from an application i'm working on.

Can anybody tell me why it doesn't exist and what can i do to restore its existence.

The file is created by the app, not by the core client. Are you initializing diagnostics?

[Maybe this should be moved to API section]

---

The file is created by the app, not by the core client. Are you initializing diagnostics?

[Maybe this should be moved to API section]

The app fills stderr.txt by writing to its stderr / handle 2 but the redirect of that handle to a fresh created disk file is done in app_start.C, just before it starts the application (currently line 680).

I don't think that it is an API issue.

(p.s.: it's in the Unix/Linux/Mac #if-#else branch of app_start.C, for Windows your assumption would have been correct)

I thought stderr.txt captures the activities of the application and is located under the slots directory in boinc-client. But it's missing in my client. I am not sure if application creates the file (it surely edits the file).

In any case, do you what should I do to get the stderr to print the outputs in stderr.txt at the client end?

I thought stderr.txt captures the activities of the application and is located under the slots directory in boinc-client.

You're right. It captures the console output of the "error channel" and redirects it to a file. Under Linux, the core client should handle that redirect.

But it's missing in my client. I am not sure if application creates the file (it surely edits the file).

Under windows, the project application (API) does that in the initialisation. Under Unix/Mac/Linux, the core client takes over that part.

In any case, do you what should I do to get the stderr to print the outputs in stderr.txt at the client end?

I don't have an idea, just some more questions ;-)

Could it be a permission thing? (chmod 777 all slot subdirectories for one test)

Do other projects have a stderr in their slot? If that is not the case, it might be a problem of your core client built.

p.s.: One more, could you check the core client log files for the output you would have expected in your applications stderr.txt? If it is there, the redirect to the slot might not have worked or is completely missing in your core client built.

In none of those cases I could imagine it is an issue with your application btw.