Lam Wei Li

@yelichi Would you mind trying again with `[email protected]`? I tried the following code snippet and was unable to replicate your issue on Windows. ```javascript const log4js = require("log4js"); log4js.configure({ appenders:...

@hugo048 I believe your issue is due to the `WriteStream` handler not being closed. I am able to replicate using some simple NodeJS codes (not involving `log4js`). A short code...

@yanmofeixi When `backups=1` (or `numBackups=1`), `log4js` will only have the hot file (`cpp.log`) and the backup (`cpp.log.1`). During housekeeping/rollover, log4js will detect matching filenames and delete the excess files. In...

**What is your `log4js` version and configuration passed into `log4js.configure()`?** I have no idea how the excess file is created. There could be a number of reasons and I have...

@yanmofeixi This is strange as the code I've provided is sort of an unit test and how `log4js`is normally used. There shouldn't be any randomness involved. Unfortunately, it is hard...

Hmm, I'm not exactly sure about the history of the migration paths. Probably take a look at the [migration guide](https://log4js-node.github.io/log4js-node/migration-guide.html)? It does seem like there are not many API differences...

> Advise: would it make sense to also include something like `%F` for obtaining the full, unsplitted name? Can you provide a sample for my understanding? 🤗

I see. So `%F` would be the entire group of the regexp? I think that's a good idea 👍, so there is no need to do concatenation manually. You must...

Anyway, I have also edited your original post with a table for clarity for whoever might be reading in future. Feel free to correct it if it's wrong.

Target by end of the week. 🤗