> Runtime.exec and ProcessBuilder.start methods create a new operating system
> process with the program and arguments. Many applications configure a logging
> subsystem to monitor application events. Logging a process start message with
> the program, arguments, and stack trace can identify the
On Tue, 14 Mar 2023 18:08:08 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wi
> Runtime.exec and ProcessBuilder.start methods create a new operating system
> process with the program and arguments. Many applications configure a logging
> subsystem to monitor application events. Logging a process start message with
> the program, arguments, and stack trace can identify the
On Fri, 10 Mar 2023 21:34:56 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wi
On Fri, 10 Mar 2023 21:34:56 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wi
> Runtime.exec and ProcessBuilder.start methods create a new operating system
> process with the program and arguments. Many applications configure a logging
> subsystem to monitor application events. Logging a process start message with
> the program, arguments, and stack trace can identify the
On Fri, 10 Mar 2023 15:27:54 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wi
> Runtime.exec and ProcessBuilder.start methods create a new operating system
> process with the program and arguments. Many applications configure a logging
> subsystem to monitor application events. Logging a process start message with
> the program, arguments, and stack trace can identify the
On Fri, 10 Mar 2023 15:11:50 GMT, Roger Riggs wrote:
>> test/jdk/java/lang/ProcessBuilder/ProcessStartLoggingTest.java line 81:
>>
>>> 79: File nullDirectory = null;
>>> 80: File thisDirectory = new File(".");
>>> 81:
>>
>> I started to heavily use different `@test` sections wi
On Thu, 9 Mar 2023 20:24:11 GMT, Thomas Stuefe wrote:
>> Roger Riggs has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Revise logging of ProcessBuilder.start to support DEBUG and TRACE logging.
>> Revise the implNote to include a warning
On Fri, 10 Mar 2023 00:01:51 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wi
> Runtime.exec and ProcessBuilder.start methods create a new operating system
> process with the program and arguments. Many applications configure a logging
> subsystem to monitor application events. Logging a process start message with
> the program, arguments, and stack trace can identify the
On Thu, 9 Mar 2023 19:53:07 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wit
On Sun, 5 Mar 2023 06:14:49 GMT, Thomas Stuefe wrote:
>> Roger Riggs has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Add javadoc @implNote to Runtime.exec and ProcessBuilder methods
>
> Hi Roger,
>
> I think to be even more useful it co
> Runtime.exec and ProcessBuilder.start methods create a new operating system
> process with the program and arguments. Many applications configure a logging
> subsystem to monitor application events. Logging a process start message with
> the program, arguments, and stack trace can identify the
On Sun, 5 Mar 2023 06:14:49 GMT, Thomas Stuefe wrote:
> I think to be even more useful it could make sense to print the current
> directory the child is started in as well as the env var array, possibly only
> with a finer logging level.
There are concerns about exposing potentially sensitive
On Mon, 6 Mar 2023 12:44:57 GMT, Daniel Fuchs wrote:
>> Roger Riggs has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Add javadoc @implNote to Runtime.exec and ProcessBuilder methods
>
> src/java.base/share/classes/java/lang/ProcessBuilder
On Sat, 4 Mar 2023 14:22:33 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wit
On Sat, 4 Mar 2023 14:22:33 GMT, Roger Riggs wrote:
>> Runtime.exec and ProcessBuilder.start methods create a new operating system
>> process with the program and arguments. Many applications configure a
>> logging subsystem to monitor application events. Logging a process start
>> message wit
> Runtime.exec and ProcessBuilder.start methods create a new operating system
> process with the program and arguments. Many applications configure a logging
> subsystem to monitor application events. Logging a process start message with
> the program, arguments, and stack trace can identify the
Runtime.exec and ProcessBuilder.start methods create a new operating system
process with the program and arguments. Many applications configure a logging
subsystem to monitor application events. Logging a process start message with
the program, arguments, and stack trace can identify the caller
21 matches
Mail list logo
