linux – debian GFS2 clustered file system dlm daemon missing

I am configuring a GFS2 clustered file system on Debian 10, referring to However, dlm daemon is missing, so I skipped dlm-related process. After configuring only corosync settings, doing mkfs.gfs2, and mounting, the following error appears.

dlm : no local IP address has been set
dllm : cannot start dlm lowcomms -107
gfs2 : fsid=cluster:disk : dlm_new_lockspace error -107
mount /test : mount (2) system call failed: Transport endpoint is not connected.

dlm service is required in this configuration? Then how can I get dlm service? I can’t find any package related dlm in debian 10.

linux – Transmission Daemon running under custom user trying to load config from wrong path

I have transmission daemon 2.94 running as a service on a Debian 10 machine.

I changed the user running transmission daemon from default debian-transmission to www-data Apache user, since I want the save files to be readable by Apache and the opposite, Apache files to be readable by transmission.

To do that, I changed to the user setting from the following config files:

  • User=www-data in /lib/systemd/system/transmission-daemon.service
  • USER=www-data in /etc/init.d/transmission-daemon
  • setuid www-data and setgid www-data in /etc/init/transmission-daemon.conf

The transmission JSON config file still resides in /etc/transmission-daemon/settings.json. I made sure both directories /var/lib/transmission-daemon and /etc/transmission-daemon were owned by the new user www-data.

But when I relaunch the service with sudo systemctl start transmission-daemon or sudo service transmission-daemon start, I get the following in the transmission logs:

Couldn't create "/var/www/.config": Permission denied (file-posix.c:189)
Couldn't read "/var/www/.config/transmission-daemon/settings.json": No such file or directory (utils.c:238)
Couldn't save temporary file "/var/www/.config/transmission-daemon/settings.json.tmp.jq3qtN": No such file or directory (variant.c:1285)

…and other similar errors.

So it would seem transmission-daemon is trying to use the www-data user home path and recreate its config directory here.

Why is that and how can I make transmission using the previous default config path? I don’t see any transmission configuration depending on the user home path.

Side question: what is the difference between all those three config files where you set up the user running the service?

App Windows – DAEMON Tools Lite Multilingual

File Size : 41.1 Mb

DAEMON Tools Lite offers easy tools for making simple disc image files and emulating virtual CD, DVD and Blu-ray drives.​

It is an advanced application for Microsoft Windows which provides one of the best optical media emulation in the industry. DAEMON Tools enables you to convert your physical CD/DVD/Blu-ray discs into “virtual discs” so called “images”. You can use your CD/DVD/BD images as if they were already burned to CD/DVD/Blu-Ray. It also emulated up to 4 virtual CD/DVD/BD drives, so you can mount (insert) and unmount (eject) images. Virtual drives will appear in your OS just like real ones. Select a virtual drive then choose a disc image you want to mount. Find the created virtual drive with mounted disc image in My Computer and start working.
With DAEMON Tools Lite you can create ISO, MDS/MDF and MDX image files from original discs inserted in physical CD, DVD and Blu-ray drives.

Do you want to protect your image content from unauthorized use? DAEMON Tools enables you to set unique password and only the ones who know it will be able to mount that image and get all contained data. If you want images to take less hard drive space just enable “Compress image data” option before start disc imaging process. You could also use images created with other programs. DAEMON Tools products work with variety of image types.

Mount *.mdx, *.mds/*.mdf, *.iso, *.b5t, *.b6t, *.bwt, *.ccd, *.cdi, *.bin/*.cue, *.ape/*.cue, *.flac/*.cue, *.nrg, *.isz disc images to a virtual drive

Create .iso, *.mds/*.mdf and *.mdx images of CD, DVD, Blu-ray discs

Compress your images

Protect images with password

Manage your Image Collection

Create up to 4 virtual devices (DT and SCSI in all) to mount several images simultaneously

Customize virtual drives: change a drive letter, DVD region, etc

Get quick access to all functionalities via program icon in the System Tray

Use File Associations to mount images right from Windows Explorer

Use powerful Command Line Interface for automation purposes

Perform basic actions via handy DAEMON Tools Gadget on Windows Desktop

Keep track of the disc image usage statistic

Find out Top 100 most popular images

Search other discs similar to yours

Search for disc images that you are missing

Browsing for most relevant gameplay videos and much more


linux – How to forward my SSH agent to a remote docker daemon?

Accessing an SSH agent local to the docker daemon during build is a popular and well-documented use case. I need a remote docker daemon to access my local SSH agent. SSH agent forwarding generally provides remote access to a local agent.

But the remote builder insists that no SSH agent is running when I forward it and attempt to mount it in my Dockerfile:

$ cat ~/.ssh/config
Host <my-docker-daemon-host>
  ForwardAgent yes

$ ssh-add -l
256 SHA256:... ... (ED25519)

$ docker --version
Docker version 19.03.13, build 4484c46d9d

$ DOCKER_BUILDKIT=1 docker -H ssh://root@<my-docker-daemon-host> build --ssh default .
#63 (test-image 33/51) RUN --mount=type=ssh ssh-add -l
#63 0.427 Error connecting to agent: No such file or directory
#63 ERROR: executor failed running (/bin/sh -c ssh-add -l): runc did not terminate sucessfully

How can I direct the remote docker daemon to mount a forwarded SSH agent when executing RUN --mount=type=ssh in a Dockerfile?

lightning network daemon – How do I explore the current commitment transaction for a channel?

I would like to see how a commitment transaction for a given payment channel looks like (without actually closing the channels and transmitting the transaction to the network 🙂

I assume that all of the building blocks (such as balances) are somewhere in channel.db. Is there a way to quickly get this information out and construct the commitment transaction out of it without much coding?

crashes – Hexedit to fix camera daemon crash

I’m trying to get the camera working for the LG G4 (msm8992) in Android 10 (for almost a year now.

Can someone help me hexediting the camera blob (system/vendor/lib/
This blob seems to be a common cause of camera crashes:

I dont know what to look for to modify in the blob. I would like some guidance on what to look for once hexediting and debugging to find why the lib is causing the camera to fail..

Here is my log of the crashes during the startup of the camera app:

And the two tombstones :

These are the device trees :

How does the rsync daemon handle simultaneous access to the file?

In order to give different permission to different users. I have module like this:

    path = /data/cvs
    comment = example
    uid = rsyncbackup
    gid = rsyncbackup
    read only = no
    list = yes
    auth users = , guest1:ro, guest2:ro, admin1:rw, admin2:rw
    secrets file = /etc/rsyncd.secrets
  • There will not be any problem if both guest1 and guest2 are connected, since they are all read only.
  • What will happen if both guest1 and admin1 connect to the daemon? since admin1 is modifying the files and the guest1 is reading from it. Will there be racing? I can of course limit the max connection to 1. But this is inefficient when only ro users want to connect. Is there lock to prevent other user to connect when a rw user connect to the daemon? Is there options to only allow single rw user to connect but allow multiple ro users to connect?
  • what will happen if both admin1 and admin2 connect to the daemon? Both admin want to modify the path, is there lock prevent later one modify anything before the first one drops connection? Or is there lock to prevent multiple user modify the same file but still allow them modify different files?
  • what will happen if multiple ips try to connect to the daemon with same user for example admin1?

daemon – Configure a server program to restart after crash

I have a web service that runs on Linux. Is there a conventional way to ensure the server is restarted in the event of a crash?

I suppose I might have a shell script which does something like this:

while true; do ./myserver; done

But I think the need to attach the script to a session makes this a poor solution. What is the correct way to do this?

Should there be a daemon process which spawns the server as another daemon? Or is there a better way?

arch linux – connecting bluetooth device seems to cause bluetooth daemon to fail

Running Arch Linux, bluez.

I honest to god can’t figure out what’s going on here. Here’s the result of trying to connect my headset with bluetoothctl.

Agent registered
[CHG] Controller BC:14:EF:64:0E:18 Pairable: yes
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# devices
Device 30:21:72:56:31:6A CROSLEY CR8005
Device EB:06:EF:88:70:1B Mpow H7
Device 20:74:CF:14:D1:DC TREKZ Titanium by AfterShokz
Device 88:B8:D8:03:85:A3 JLab BT
[CHG] Device EB:06:EF:88:70:1B Connected: yes
Agent unregistered
[DEL] Controller BC:14:EF:64:0E:18 pupcomp [default]
Waiting to connect to bluetoothd...

When I attempt to connect with Blueman it DOES connect for half a second, and then gives me:

Connection to BlueZ failed

BlueS daemon is not running, blueman-manager cannot continue. This probably means there were no Bluetooth adapters detected or Bluetooth daemon was not started.

btmgt shows the dongle as powered, so im assuming its not a failure there.

hci0:   Primary controller
    addr BC:14:EF:64:0E:18 version 6 manufacturer 15 class 0x3c0104
    supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration 

I’ve seen similar threads in other places, but none of those solutions worked. I’ve tried reinstalling bluez, bluez-utils, blueman, pulseaudio-bluetooth and pulseaudio. This has not solved the problem. Hopefully the problem is obvious and I’m just missing it. It seems like some issue with the daemon, but I don’t know how to solve it.

hard drive – Use an External USB SSD before logon (daemon)

I noticed that after a system reboot my new USB SSD (SanDisk Extreme Portable SSD) attached via USB-C to an MacMini 2020 is not available until the first user has logged on.

On this MacMini a daemon is running which requires access to the external USB drive directly after a reboot before any user has logged on.

What do I have to configure in Catalina to make my USB SSD available before the first user has logged on?