mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-11-02 11:21:12 +00:00
8f10c1e77f
Libvirt uses a domain name to fill in owner_name in sanlock_options in virLockManagerSanlockAcquire. Unfortunately, owner_name is limited to SANLK_NAME_LEN characters (including trailing '\0'), which means domains with longer names fail to start when sanlock is enabled. However, we can truncate the name when setting owner_name as explained by sanlock's author: Setting sanlk_options or the owner_name is unnecessary, and has very little to no benefit. If you do provide something in owner_name, it can be anything, sanlock doesn't care or use it. If you run the command "sanlock status", the output will display a list of clients connected to the sanlock daemon. This client list is displayed as "pid owner_name" if the client has provided an owner_name via sanlk_options. This debugging output is the only usage of owner_name, so its only benefit is to potentially provide a more human friendly output for debugging purposes. |
||
|---|---|---|
| .. | ||
| domain_lock.c | ||
| domain_lock.h | ||
| libvirt_lockd.aug | ||
| libvirt_sanlock.aug | ||
| lock_daemon_config.c | ||
| lock_daemon_config.h | ||
| lock_daemon_dispatch.c | ||
| lock_daemon_dispatch.h | ||
| lock_daemon.c | ||
| lock_daemon.h | ||
| lock_driver_lockd.c | ||
| lock_driver_nop.c | ||
| lock_driver_nop.h | ||
| lock_driver_sanlock.c | ||
| lock_driver.h | ||
| lock_manager.c | ||
| lock_manager.h | ||
| lock_protocol.x | ||
| lockd.conf | ||
| sanlock_helper.c | ||
| sanlock.conf | ||
| test_libvirt_lockd.aug.in | ||
| test_libvirt_sanlock.aug.in | ||
| test_virtlockd.aug.in | ||
| virtlockd.aug | ||
| virtlockd.conf | ||
| virtlockd.init.in | ||
| virtlockd.pod.in | ||
| virtlockd.service.in | ||
| virtlockd.socket.in | ||
| virtlockd.sysconf | ||