Hi,
Indeed, those are HLS streams. They can be there because 2 possible reasons:
1. You created them via createHlsStream
2. You activated autoHLS inside the configuration file.
If #2 is true, that means that for each and every input stream you will have an HLS associated with it.
It is legal to have multiple OFHLS streams. Each of those streams will have an unique id. Depending on who created them (autoHLS or cretehlsstream), you know exactly what is the purpose of its existence and also if it can be safely and permanently removed.
if you created the HLS streams with createHlsStream, than you should do removeConfig id=<configId> where configId is not uniqueStreamId from liststreams. It is the configId returned from listconfig.
If you activated autoHLS, that removeConfig will work to some extent (will do its job, will close the config and the corresponding stream), but once a new stream comes in, it will spawn a new HLS immediately.
So, to further make things clear:
config – an entity like a blueprint of the future input or output stream. It is not the stream itself. only its settings.
stream – the entity spawned when the config entity is evaluated and executed successfully
Those 2 kinds of entities have different IDs. Do not mix them. configId=1 is not the same thing as uniqueStreamId=1
Best regards,
Andrei