remove -t option from logger start

boards/modalai/voxl2/target/voxl-px4-hitl-start

@@ -91,7 +91,7 @@ mavlink stream -u 14556 -s GLOBAL_POSITION_INT -r 30
 mavlink start -x -u 14558 -o 14559 -r 100000 -n lo
 
 # Start logging and use timestamps for log files when possible.
-logger start -t -b 256
+logger start -b 256
 
 /bin/sleep 1
 

boards/modalai/voxl2/target/voxl-px4-start

@@ -240,7 +240,7 @@ mavlink start -x -u 14558 -o 14559 -r 100000 -n lo
 # because if power is removed without stopping the logger gracefully then
 # the log file may be corrupted. Rather than using "-e" option it's better
 # to use the SDLOG_MODE to do that.
-logger start -t -b 256
+logger start -b 256
 
 mavlink boot_complete
 

docs/en/modules/modules_system.md

@@ -467,7 +467,7 @@ the mission log). It should be large to avoid dropouts.
 ### Examples
 Typical usage to start logging immediately:
 ```
-logger start -e -t
+logger start -e
 ```
 
 Or if already running:

posix-configs/SITL/init/test/test_imu_filtering

@@ -43,7 +43,7 @@ fake_imu start
 sensors start
 gyro_fft start
 
-logger start -f -t -b 10000 -p sensor_gyro
+logger start -f -b 10000 -p sensor_gyro
 logger on
 
 echo "Running for 10 seconds"

posix-configs/SITL/init/test/test_shutdown

@@ -37,7 +37,7 @@ control_allocator start
 
 ver all
 
-logger start -e -t
+logger start -e
 
 mavlink boot_complete
 

posix-configs/bbblue/px4.config

@@ -75,6 +75,6 @@ sleep 1
 control_allocator start
 linux_pwm_out start
 
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/bbblue/px4_fw.config

@@ -70,6 +70,6 @@ rc_input start -d /dev/ttyS4
 control_allocator start
 linux_pwm_out start
 
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/rpi/navigator/sub.config

@@ -44,6 +44,6 @@ uuv_att_control start
 uuv_pos_control start
 
 mavlink start -x -u 14556 -r 1000000 -p
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/rpi/pilotpi_fw.config

@@ -70,6 +70,6 @@ mavlink start -x -u 14556 -r 1000000 -p
 # Telem
 mavlink start -x -Z -d /dev/ttySC1
 
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/rpi/pilotpi_mc.config

@@ -68,6 +68,6 @@ mavlink start -x -u 14556 -r 1000000 -p
 # Telem
 mavlink start -x -Z -d /dev/ttySC1
 
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/rpi/px4.config

@@ -59,6 +59,6 @@ navio_sysfs_rc_in start
 linux_pwm_out start
 control_allocator start
 
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/rpi/px4_fw.config

@@ -57,6 +57,6 @@ navio_sysfs_rc_in start
 linux_pwm_out start
 control_allocator start
 
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/rpi/px4_hil.config

@@ -39,6 +39,6 @@ navio_sysfs_rc_in start
 pwm_out_sim start
 control_allocator start
 
-logger start -t -b 200
+logger start -b 200
 
 mavlink boot_complete

posix-configs/rpi/px4_test.config

@@ -56,7 +56,7 @@ navio_sysfs_rc_in start
 linux_pwm_out start
 control_allocator start
 
-logger start -t -f -b 200
+logger start -f -b 200
 
 mavlink boot_complete
 

src/modules/logger/logger.cpp

@@ -2476,7 +2476,7 @@ the mission log). It should be large to avoid dropouts.
 
 ### Examples
 Typical usage to start logging immediately:
-$ logger start -e -t
+$ logger start -e
 
 Or if already running:
 $ logger on