An alternative solution that I found is by storing the PID:

ros2 bag record /topic_name
BAG_PID=$!
sleep time_length
kill $BAG_PID

@paoloelle, @nicolaloi Could you please provide a real-world use cases/examples when this functionality with requested new --max-recording-duration, --max-recording-size and --max-recording-messages CLI options would be usefull?

Why one would need to record for some time and then automatically stop at the first hand?

Why not send SIG_INT or use a service call to stop recording when needed as
ros2 service call /rosbag2_recorder/stop rosbag2_interfaces/Stop ?

@MichaelOrlov I'm running an evolutionary algorithm using ROS 2 and Gazebo. In my setup, I need to run a huge amount of simulations (each of them lasts 1 minute) and be able to stop/resume a simulation, change some parameters, and record the data for each single run (using ros2 bag). I do that in an automated way by using a bash file. I thought that having an option that allows me to specify the duration of my recording instead of having to explicitly kill the process would be a more practical way to stop the recording. Also, my idea is to run these simulations on a computing cluster, and I’m not sure I will have the privileges to kill processes at will.

Why one would need to record for some time and then automatically stop at the first hand?

Why not send SIG_INT or use a service call to stop recording when needed as ros2 service call /rosbag2_recorder/stop rosbag2_interfaces/Stop ?

Does this service already exist? Sorry, but I didn't know about that.