dougsland

[root@localhost ~]# journalctl -r |  grep -i systemd
Mar 05 06:21:05 localhost.localdomain systemd[547]: Finished Cleanup of User's Temporary Files and Directories.
Mar 05 06:21:05 localhost.localdomain systemd[547]: Starting Cleanup of User's Temporary Files and Directories...
Mar 05 06:21:05 localhost.localdomain systemd[547]: Created slice User Background Tasks Slice.
Mar 05 06:16:20 localhost.localdomain systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Mar 05 06:15:55 localhost.localdomain systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 05 06:15:50 localhost.localdomain systemd[1]: Started Session 1 of User root.
Mar 05 06:15:50 localhost.localdomain systemd[1]: Started User Manager for UID 0.
Mar 05 06:15:50 localhost.localdomain systemd[547]: Startup finished in 282ms.
Mar 05 06:15:50 localhost.localdomain systemd[547]: Reached target Main User Target.

dougsland

Evil BlueChi-Agent

This gist shows a basic frame on how to implement a bluechi-agent for testing purposes only, e.g. as intended in containers/qm#234.

Using Python + DasBus

The python example does not include emitting signals as defined in the introspection data.

Running the example evil_bluechi_agent.py:

dougsland

dnf install gcc dbus-devel -y
gcc -o list_nodes list_nodes.c -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include/ -ldbus-1


#include <dbus/dbus.h>
#include <stdio.h>
#include <stdlib.h>

void handle_structure(DBusMessageIter *structIter) {
    int typeInStruct;

dougsland

dnf install g++ dbus-devel -y
g++ -o list_nodes list_nodes.cpp -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include/ -ldbus-1


#include <dbus/dbus.h>
#include <iostream>

void handle_structure(DBusMessageIter *structIter) {
    int typeInStruct;
    while ((typeInStruct = dbus_message_iter_get_arg_type(

dougsland

# Rust

Rust developers can take advance of **dbus-codegen-rust** to generate a Rust module
and use,tag,release in any pace it's appropriate to their project.

## Generating bluechi module

Make sure a BlueChi node is running and execute the below commands.
``` bash
# dnf install rust cargo

dougsland

# busctl introspect org.eclipse.bluechi  /org/eclipse/bluechi
NAME                                TYPE      SIGNATURE RESULT/VALUE   FLAGS
org.eclipse.bluechi.Manager         interface -         -              -
.CreateMonitor                      method    -         o              -
.DisableMetrics                     method    -         -              -
.EnableMetrics                      method    -         -              -
.GetNode                            method    s         o              -
.ListNodes                          method    -         a(sos)         -
.ListUnits                          method    -         a(sssssssouso) -
.Ping                               method    s         s              -

dougsland

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

dougsland

# Note: not sure who wrote this, but thank you
# Note: ~/.ssh/environment should not be used, as it
#       already has a different purpose in SSH.

env=~/.ssh/agent.env

# Note: Don't bother checking SSH_AGENT_PID. It's not used
#       by SSH itself, and it might even be incorrect
#       (for example, when using agent-forwarding over SSH).

dougsland

NetworkManager WiFi Power Saving

NetworkManager supports WiFi powersaving but the function is rather undocumented.

From the source code: wifi.powersave can have the following value:

• NM_SETTING_WIRELESS_POWERSAVE_DEFAULT (0): use the default value
• NM_SETTING_WIRELESS_POWERSAVE_IGNORE (1): don't touch existing setting
• NM_SETTING_WIRELESS_POWERSAVE_DISABLE (2): disable powersave

dougsland

Typing vagrant from the command line will display a list of all available commands.

Be sure that you are in the same directory as the Vagrantfile when running these commands!

Creating a VM

• vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
• vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.

Starting a VM

• vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)