Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 18.191.120.131
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
python-slip-0.4.0 /
dbus /
example /
Delete
Unzip
Name
Size
Permission
Date
Action
Makefile
1.43
KB
-rw-r--r--
2013-03-08 10:55
README
1019
B
-rw-r--r--
2013-03-08 10:55
example-conf-client.py
1.81
KB
-rw-r--r--
2013-03-08 10:55
example-conf-mechanism.py
2.29
KB
-rw-r--r--
2013-03-08 10:55
import_marker.py
0
B
-rw-r--r--
2013-03-08 10:55
org.fedoraproject.slip.example.mechanism.conf
527
B
-rw-r--r--
2013-03-08 10:55
org.fedoraproject.slip.example.mechanism.service
122
B
-rw-r--r--
2013-03-08 10:55
org.fedoraproject.slip.example.policy
963
B
-rw-r--r--
2013-03-08 10:55
Save
Rename
To use this example code, you have to install some files into system locations. Run "make example_install" as root from this directory to do that, "make example_uninstall" will uninstall these files again. After installing, there are two ways to run the example service right now: 1. Run "./example-conf-mechanism.py" as root from this directory. This will let you see the output of the example mechanism and observe it exiting after the client exited. 2. With SELinux permissive or disabled(*), the system message bus will start up the installed example service from the installed location, if it's not already running (see 1.). This will not let you see its output and you will have to look at the list of running processes to see that it exits after the client. (*): The SELinux policy only allows the system message bus daemon to start select binaries, this example service isn't covered. Then you can run "./example-conf-client.py" as a normal user which will call a set of methods on the service mechanism.