Re: multiple programs sharing redirected STDERR

You mentioned "users" (plural)... if two or more people are using the same script simultaneously, and "errfile.txt" is the same path for all of them, you'll have trouble (users will be misinformed and confused by the file's content).

That's easy to fix by making sure that every run uses a unique file name for its log file.

Comment on Re: multiple programs sharing redirected STDERR

Replies are listed 'Best First'.
Re^2: multiple programs sharing redirected STDERR by ff (Hermit) on Apr 27, 2005 at 03:23 UTC
I should say, I'm "hoping" for users. :-) The program is a single-user tool for a W32 platform. It installs in a user-specified/owned folder and therefore, even with the same relative path name, would be unique from user to user. When the need arises to get this "Enterprise-ready", it will still be a matter of each user's config files (and thus his/her log file) being in their own directory/folder. You make a good point that I hadn't considered directly. But also, by your going along with "one log file per user/run", it looks okay to you to proceed with this sort of STDERR inheritance scheme. :-)	[reply]

Replies are listed 'Best First'.

Re^2: multiple programs sharing redirected STDERR
by ff (Hermit) on Apr 27, 2005 at 03:23 UTC

The program is a single-user tool for a W32 platform. It installs in a user-specified/owned folder and therefore, even with the same relative path name, would be unique from user to user. When the need arises to get this "Enterprise-ready", it will still be a matter of each user's config files (and thus his/her log file) being in their own directory/folder. You make a good point that I hadn't considered directly.

But also, by your going along with "one log file per user/run", it looks okay to you to proceed with this sort of STDERR inheritance scheme. :-)

[reply]