FM / example

/usr/share/doc/python3-slip-dbus/example/

/usr/share/doc/python3-slip-dbus/example

Name	Size	Mode	Actions
example-conf-client.py	1820	0644	edit dl rm
example-conf-mechanism.py	2424	0644	edit dl rm
import_marker.py	0	0644	edit dl rm
Makefile	1460	0644	edit dl rm
org.fedoraproject.slip.example.mechanism.conf	527	0644	edit dl rm
org.fedoraproject.slip.example.mechanism.service	122	0644	edit dl rm
org.fedoraproject.slip.example.policy	963	0644	edit dl rm
README	1019	0644	edit dl rm

Edit: /usr/share/doc/python3-slip-dbus/example/README (1019B)

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.

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.