ow-numbered
>>> PIDs then this won't be unique. (With the current startup timestamp,
>>> you will probably use %p for pid in the file as well, in case JVMs
>>> start at the same moment.)
>>>
>>> Thanks
>>>
>>> Kevin
>>>
>&g
g
*Subject:* RE: [EXTERNAL] Proposal to change the behavior of the
timestamp place holder (%t) in log file paths
CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you can confirm the sender
and know the content is safe.
On 1/29/25
t: RE: [EXTERNAL] Proposal to change the behavior of the timestamp place
holder (%t) in log file paths
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
On 1/29/25 5:56 PM, David H
rtup timestamp,
you will probably use %p for pid in the file as well, in case JVMs
start at the same moment.)
Thanks
Kevin
*From:*serviceability-dev *On
Behalf Of *Kemper, William
*Sent:* Tuesday, January 28, 2025 7:54 PM
*To:* serviceability-dev@openjdk.org
*Subject:* Proposal to change th
file as well, in case JVMs
start at the same moment.)
Thanks
Kevin
*From:*serviceability-dev *On
Behalf Of *Kemper, William
*Sent:* Tuesday, January 28, 2025 7:54 PM
*To:* serviceability-dev@openjdk.org
*Subject:* Proposal to change the behavior of the timestamp place
holder (%t) in log file
org
Subject: Proposal to change the behavior of the timestamp place holder (%t) in
log file paths
The timestamp place holder in a log filename currently expands to the startup
time of the JVM. When the log is rotated, the filename containing this
timestamp is suffixed with a file number. My colle
The timestamp place holder in a log filename currently expands to the startup
time of the JVM. When the log is rotated, the filename containing this
timestamp is suffixed with a file number. My colleagues had expected the
placeholder to be evaluated when the current log file is rotated. They exp
