ossrs / srs

SRS is a simple, high-efficiency, real-time video server supporting RTMP, WebRTC, HLS, HTTP-FLV, SRT, MPEG-DASH, and GB28181.

Home Page:https://ossrs.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Support log splitting, LOG ROTATE

winlinvip opened this issue · comments

Log rotation is now supported.
SIGUSR1 is used for log rotation in nginx and has been corrected. Persistence log is not supported through signals, only through the API.
Reference: 2955b1f

TRANS_BY_GPT3

persistence log does not pass through signals, only supported through API.
-- In https://github.com/ossrs/srs/wiki/v3_CN_HTTPApi#persistence-config
In this document, I didn't see the API calling method for adjusting the persistence-config after modification?

TRANS_BY_GPT3

@ajaxhe The RAW API has an Update function, which means that when calling RawApi, it will automatically persist the Config. SRS does not provide a separate API Persistence Config, so it is not useful, right?

TRANS_BY_GPT3

Ah, indeed, it's my fault for not paying attention to the updated configuration file after the update... This is great, there are no issues at all.

When using the API to adjust the configuration, there is another confusion:
In the RAW Vhost configuration section, it seems that only a format like key-value is supported when configuring. Suppose I want to add a new vhost and configure a complete block configuration for HLS, it seems that using the API is not a good solution.
For example, if I want to add the complete configuration for hls.ajaxhe.com using the API, is there any good method? Thank you~

vhost hls.ajaxhe.com {
    hls {
        enabled on;            
        hls_fragment 10;
        hls_window 60;         
        hls_path ./objs/nginx/html;     
        hls_m3u8_file [app]/[stream].m3u8;
        hls_ts_file [app]/[stream]-[seq].ts;
    }
}

TRANS_BY_GPT3

The RAW API needs improvement, currently it provides mainly key-value modification.

TRANS_BY_GPT3

Understood, received, thank you~

TRANS_BY_GPT3