Hi
I noticed that running s6-log as follows still creates few
archived logs:
s6-log -b s4096 n0 S0 !xz -0q /log
drwxr-x--- 5 s6log monitor 4096 Mar 22 16:36 .
drwxr-xr-x 6 root root 64 Mar 22 16:21 ..
drwxr-x--- 2 root root 118 Mar 22 16:10 env
drwx-wx-wt 2 root root 6 Mar 22 16:05 event
drwx------ 2 root root 44 Mar 22 16:22 supervise
-rwxr--r-- 1 s6log s6log 244 Mar 22 16:36 _at_40000000532d9ffd171b6042.s
-rwxr--r-- 1 s6log s6log 244 Mar 22 16:36 _at_40000000532da00b3751cbce.s
-rw-r--r-- 1 s6log s6log 1216 Mar 22 16:36 current
-rw-r----- 1 s6log s6log 0 Mar 22 16:05 lock
-rwxr-x--- 1 root root 1420 Nov 8 12:27 mark
lrwxrwxrwx 1 root root 7 Mar 22 15:25 run -> mark
-rw-r----- 1 s6log s6log 0 Mar 22 16:36 state
I thought that by using 'n0' no arhived logs will be created. I
would expect it ignore the archive processor and continuously log
to 'current', keeping it around 4096 bytes or less.
--
Vallo
Received on Sat Mar 22 2014 - 14:56:34 UTC