ELOGIND.INDEX(7)
✨ ELOGIND.INDEX ✨
okay bestie, welcome to the elogind master list 💖 this is elogind.index(7) and it's literally just every single manpage from the elogind project, alphabetically, so you can find your girl fast. no cap. it's giving ✨directory✨.
🌸 NAME 🌸
elogind.index — the full list of all manpages from the elogind project 🫶
🦋 B 🦋
busctl(1)— peek inside the bus and see what's up, like a little x-ray for D-Bus 🔍
💜 E 💜
elogind(8)— the login manager herself, main character energy 👑elogind-inhibit(1)— run a program while holding an inhibition lock, so nothing interrupts your moment 💅elogind.directives(7)— an index of every configuration directive, the master list of master listselogind.journal-fields(7)— special journal fields that get rerouted to syslog by elogind 🌀elogind.syntax(7)— the general syntax rules for elogind config files, iykykelogind.time(7)— time and date specifications, because time is fake but the format isn't ⏰
🌈 L 🌈
libelogind(3)— functions for implementing services and interacting with elogind, the dev girlies' section 🧚loginctl(1)— control the elogind login manager from the command line, your remote control fr frlogind.conf(5)— the login manager configuration files, where you set your whole vibelogind.conf.d(5)— more login manager configuration files, same energy, different directory 🎀
⭐ O ⭐
org.freedesktop.login1(5)— the D-Bus interface of elogind, where all the talking happens 🗣️
🍓 P 🍓
pam_elogind(8)— registers user sessions in the elogind login manager, PAM's little helper 🤝
✨ S ✨
okay bestie, here's the S section and it's literally stacked 💅
sd-bus(3)— a lightweight D-Bus IPC client library — it's giving lightweight, it's giving IPC, it's giving client library 💖sd-event(3)— a generic event loop implementation — the event loop that just works, no cap 🌀sd-login(3)— APIs for tracking logins — keep tabs on who's logged in, bestie 👀sd_bus_add_fallback(3)— declare properties and methods for a D-Bus path — setting up your D-Bus path with fallback energy ✨sd_bus_add_fallback_vtable(3)— declare properties and methods for a D-Bus path — same vibe, but with a vtable this time 🎀sd_bus_add_filter(3)— declare properties and methods for a D-Bus path — filter? more like slay ✨sd_bus_add_match(3)— add a match rule for incoming message dispatching — match rule so you only get the messages you want 💅sd_bus_add_match_async(3)— add a match rule for incoming message dispatching — async version, because we don't wait around 🦋sd_bus_add_node_enumerator(3)— add a node enumerator for a D-Bus object path prefix — enumerating nodes like it's your job 🌸sd_bus_add_object(3)— declare properties and methods for a D-Bus path — add an object, declare your properties, live your truth 💖sd_bus_add_object_manager(3)— add a D-Bus object manager for a D-Bus object sub-tree — managing objects and sub-trees like the main character you are 👑sd_bus_add_object_vtable(3)— declare properties and methods for a D-Bus path — vtable edition, still iconic ✨sd_bus_attach_event(3)— attach a bus connection object to an event loop — hooking your bus up to the event loop, periodt 🔗sd_bus_call(3)— invoke a D-Bus method call — make that call, bestie 📞sd_bus_call_async(3)— invoke a D-Bus method call — async, because we're busy 💅sd_bus_call_method(3)— initialize a bus message object and invoke the corresponding D-Bus method call — init the message, make the call, ate 💅sd_bus_call_method_async(3)— initialize a bus message object and invoke the corresponding D-Bus method call — async version, still slaying 🦋sd_bus_call_method_asyncv(3)— initialize a bus message object and invoke the corresponding D-Bus method call — with a va_list, because we're fancy ✨sd_bus_call_methodv(3)— initialize a bus message object and invoke the corresponding D-Bus method call — va_list edition, iconic 💖sd_bus_can_send(3)— check which types can be sent over a bus object — vibe check for types, can you send it? 💅sd_bus_close(3)— close and flush a bus connection — closing time, flush it out 🚪sd_bus_close_unref(3)— create a new bus object and create or destroy references to it — refs and unrefs, the cycle of life 🌀sd_bus_close_unrefp(3)— create a new bus object and create or destroy references to it — the pointer version, because cleanup on aisle you ✨sd_bus_creds_get_audit_login_uid(3)— retrieve fields from a credentials object — grabbing that audit login UID like it's hot 🔥sd_bus_creds_get_audit_session_id(3)— retrieve fields from a credentials object — audit session ID, got it 💅sd_bus_creds_get_augmented_mask(3)— retrieve credentials object for the specified PID — augmented mask, PID specified, we love to see it 👑sd_bus_creds_get_cgroup(3)— retrieve fields from a credentials object — cgroup field, retrieved ✨sd_bus_creds_get_cmdline(3)— retrieve fields from a credentials object — cmdline, coming right up 🍓sd_bus_creds_get_comm(3)— retrieve fields from a credentials object — comm field, got it 💖sd_bus_creds_get_description(3)— retrieve fields from a credentials object — description field, so descriptive 🌸sd_bus_creds_get_egid(3)— retrieve fields from a credentials object — effective GID, slay 💅sd_bus_creds_get_euid(3)— retrieve fields from a credentials object — effective UID, iconic ✨sd_bus_creds_get_exe(3)— retrieve fields from a credentials object — exe path, retrieved 🦋sd_bus_creds_get_fsgid(3)— retrieve fields from a credentials object — filesystem GID, got it 🎀sd_bus_creds_get_fsuid(3)— retrieve fields from a credentials object — filesystem UID, periodt 💜sd_bus_creds_get_gid(3)— retrieve fields from a credentials object — GID, retrieved 💅sd_bus_creds_get_mask(3)— retrieve credentials object for the specified PID — mask, PID, credentials object, we love a trio 👑sd_bus_creds_get_owner_uid(3)— retrieve fields from a credentials object — owner UID, got it ✨sd_bus_creds_get_pid(3)— retrieve fields from a credentials object — PID, retrieved 🍓sd_bus_creds_get_ppid(3)— retrieve fields from a credentials object — parent PID, coming through 💖sd_bus_creds_get_selinux_context(3)— retrieve fields from a credentials object — SELinux context, secure and slaying 🔥sd_bus_creds_get_session(3)— retrieve fields from a credentials object — session field, got it 💅sd_bus_creds_get_sgid(3)— retrieve fields from a credentials object — saved GID, retrieved ✨sd_bus_creds_get_slice(3)— retrieve fields from a credentials object — slice field, so slicey 🍰sd_bus_creds_get_suid(3)— retrieve fields from a credentials object — saved UID, iconic 💜sd_bus_creds_get_supplementary_gids(3)— retrieve fields from a credentials object — supplementary GIDs, the whole squad 🫶sd_bus_creds_get_tid(3)— retrieve fields from a credentials object — thread ID, got it 💅sd_bus_creds_get_tid_comm(3)— retrieve fields from a credentials object — thread comm, retrieved ✨sd_bus_creds_get_tty(3)— retrieve fields from a credentials object — TTY, terminal vibes 🖥️sd_bus_creds_get_uid(3)— retrieve fields from a credentials object — UID, retrieved 💖sd_bus_creds_get_unique_name(3)— retrieve fields from a credentials object — unique name, one of a kind ✨sd_bus_creds_get_unit(3)— retrieve fields from a credentials object — unit field, got it 🎀sd_bus_creds_get_user_slice(3)— retrieve fields from a credentials object — user slice, slaying 🍰sd_bus_creds_get_user_unit(3)— retrieve fields from a credentials object — user unit, retrieved 💅sd_bus_creds_get_well_known_names(3)— retrieve fields from a credentials object — well-known names, famous fr 💅sd_bus_creds_has_bounding_cap(3)— retrieve fields from a credentials object — bounding capability, got it ✨sd_bus_creds_has_effective_cap(3)— retrieve fields from a credentials object — effective capability, iconic 💜sd_bus_creds_has_inheritable_cap(3)— retrieve fields from a credentials object — inheritable capability, inherited 💅sd_bus_creds_has_permitted_cap(3)— retrieve fields from a credentials object — permitted capability, permitted to slay 🔥sd_bus_creds_new_from_pid(3)— retrieve credentials object for the specified PID — new creds from PID, fresh out the box 🎁sd_bus_creds_ref(3)— retrieve credentials object for the specified PID — ref it up, keep it alive 💖sd_bus_creds_unref(3)— retrieve credentials object for the specified PID — unref, let it go 🦋sd_bus_creds_unrefp(3)— retrieve credentials object for the specified PID — pointer unref, cleanup queen 👑sd_bus_default(3)— acquire a connection to a system or user bus — get that default bus connection, periodt 🚌sd_bus_default_flush_close(3)— close and flush a bus connection — default flush close, closing time 🚪sd_bus_default_system(3)— acquire a connection to a system or user bus — system bus, acquired 💅sd_bus_default_user(3)— acquire a connection to a system or user bus — user bus, acquired ✨sd_bus_destroy_t(3)— define the callback function for resource cleanup — destroy callback, cleanup crew 🧹sd_bus_detach_event(3)— attach a bus connection object to an event loop — detach from the event loop, bye 👋sd_bus_emit_interfaces_added(3)— convenience functions for emitting (standard) D-Bus signals — emit interfaces added, signal slay 📡sd_bus_emit_interfaces_added_strv(3)— convenience functions for emitting (standard) D-Bus signals — strv edition, still emitting ✨sd_bus_emit_interfaces_removed(3)— convenience functions for emitting (standard) D-Bus signals — interfaces removed, signal sent 💅sd_bus_emit_interfaces_removed_strv(3)— convenience functions for emitting (standard) D-Bus signals — strv removed, iconic 🦋sd_bus_emit_object_added(3)— convenience functions for emitting (standard) D-Bus signals — object added, signal it 🎀sd_bus_emit_object_removed(3)— convenience functions for emitting (standard) D-Bus signals — object removed, signal it 💜sd_bus_emit_properties_changed(3)— convenience functions for emitting (standard) D-Bus signals — properties changed, let them know 🔔sd_bus_emit_properties_changed_strv(3)— convenience functions for emitting (standard) D-Bus signals — strv properties changed, slay ✨sd_bus_emit_signal(3)— convenience functions for emitting (standard) D-Bus signals — emit a signal, make some noise 📢sd_bus_emit_signal_to(3)— convenience functions for emitting (standard) D-Bus signals — emit signal to someone specific, direct message 💌sd_bus_emit_signal_tov(3)— convenience functions for emitting (standard) D-Bus signals — signal to va_list, fancy 💅sd_bus_emit_signalv(3)— convenience functions for emitting (standard) D-Bus signals — signalv, va_list edition ✨sd_bus_error(3)— sd-bus error handling — error handling, but make it sd-bus 💅sd_bus_error_add_map(3)— additional sd-dbus error mappings — adding error maps, mapping it out 🗺️sd_bus_error_copy(3)— sd-bus error handling — copy that error, periodt 📋SD_BUS_ERROR_END(3)— additional sd-dbus error mappings — end of the error map, the finale 🎬sd_bus_error_free(3)— sd-bus error handling — free the error, let it go 🦋sd_bus_error_get_errno(3)— sd-bus error handling — get that errno, bestie 🔢sd_bus_error_has_name(3)— sd-bus error handling — does it have a name? yes queen 💅sd_bus_error_has_names(3)— sd-bus error handling — multiple names, checking them all ✨sd_bus_error_has_names_sentinel(3)— sd-bus error handling — sentinel edition, iconic 🎀sd_bus_error_is_set(3)— sd-bus error handling — is the error set? vibe check 💜SD_BUS_ERROR_MAKE_CONST(3)— sd-bus error handling — make a const error, constant slay 🔥sd_bus_error_map(3)— additional sd-dbus error mappings — error map, mapping errors 🗺️SD_BUS_ERROR_MAP(3)— additional sd-dbus error mappings — error map macro, uppercase energy 💅sd_bus_error_move(3)— sd-bus error handling — move that error, relocate it 🚚SD_BUS_ERROR_NULL(3)— sd-bus error handling — null error, empty vibes 🕳️sd_bus_error_set(3)— sd-bus error handling — set the error, do it 💅sd_bus_error_set_const(3)— sd-bus error handling — set a const error, unchangeable ✨sd_bus_error_set_errno(3)— sd-bus error handling — set errno error, numeric slay 🔢sd_bus_error_set_errnof(3)— sd-bus error handling — set errno with format, fancy 💅sd_bus_error_set_errnofv(3)— sd-bus error handling — errnof with va_list, extra fancy ✨sd_bus_error_setf(3)— sd-bus error handling — set error with format, formatted 💖sd_bus_error_setfv(3)— sd-bus error handling — setf with va_list, iconic 🦋sd_bus_flush(3)— close and flush a bus connection — flush it, bestie 🚽sd_bus_flush_close_unref(3)— create a new bus object and create or destroy references to it — flush, close, unref, the whole routine 💅sd_bus_flush_close_unrefp(3)— create a new bus object and create or destroy references to it — pointer version, cleanup queen 👑sd_bus_get_address(3)— set or query the address of the bus connection — get that bus address, where you at? 📍sd_bus_get_allow_interactive_authorization(3)— set or query properties of a bus object — interactive auth allowed? query it 💅sd_bus_get_bus_id(3)— configure connection mode for a bus object — get bus ID, identify yourself 🆔sd_bus_get_close_on_exit(3)— control whether to close the bus connection during the event loop exit phase — close on exit? your call 💅sd_bus_get_connected_signal(3)— control emission of local connection establishment signal on bus connections — connected signal emission, signal it 📡sd_bus_get_creds_mask(3)— control feature negotiation on bus connections — creds mask, feature negotiation 💅sd_bus_get_current_handler(3)— query information of the callback a bus object is currently running — current handler, what's running? 👀sd_bus_get_current_message(3)— query information of the callback a bus object is currently running — current message, got it 💌sd_bus_get_current_slot(3)— query information of the callback a bus object is currently running — current slot, slay 🎰sd_bus_get_current_userdata(3)— query information of the callback a bus object is currently running — current userdata, user data vibes 💾sd_bus_get_description(3)— set or query properties of a bus object — get description, describe it 💅sd_bus_get_event(3)— attach a bus connection object to an event loop — get the event, event loop energy 🌀sd_bus_get_events(3)— get the file descriptor, I/O events and timeout to wait for from a message bus object — events, fd, timeout, the trifecta ✨sd_bus_get_exit_on_disconnect(3)— control the exit behavior when the bus object disconnects — exit on disconnect? your choice 💅sd_bus_get_fd(3)— get the file descriptor, I/O events and timeout to wait for from a message bus object — get that fd, file descriptor realness 📁sd_bus_get_method_call_timeout(3)— set or query the default D-Bus method call timeout of a bus object — method call timeout, how long we waiting? ⏳sd_bus_get_n_queued_read(3)— get the number of pending bus messages in the read and write queues of a bus connection object — queued read count, how many? 🔢sd_bus_get_n_queued_write(3)— get the number of pending bus messages in the read and write queues of a bus connection object — queued write count, got it 💅sd_bus_get_name_creds(3)— query bus client credentials — name creds, who dis? 🕵️sd_bus_get_name_machine_id(3)— retrieve a bus client's machine identity — machine ID, identity theft but legal 💻sd_bus_get_owner_creds(3)— query bus client credentials — owner creds, the owner's credentials 👑sd_bus_get_property(3)— set or query D-Bus service properties — get property, property vibes 🏠sd_bus_get_property_string(3)— set or query D-Bus service properties — property string, string it along 🧵sd_bus_get_property_strv(3)— set or query D-Bus service properties — property strv, string array slay ✨sd_bus_get_property_trivial(3)— set or query D-Bus service properties — trivial property, simple but iconic 💅sd_bus_get_scope(3)— set or query properties of a bus object — get scope, scope it out 🔭sd_bus_get_sender(3)— configure default sender for outgoing messages — get sender, who sent it? 📨sd_bus_get_tid(3)— set or query properties of a bus object — get TID, thread ID realness 🧵sd_bus_get_timeout(3)— get the file descriptor, I/O events and timeout to wait for from a message bus object — timeout, how long we waiting? ⏳sd_bus_get_unique_name(3)— set or query properties of a bus object — unique name, one of a kind 💎sd_bus_get_watch_bind(3)— control socket binding watching on bus connections — watch bind, watching the socket 👀sd_bus_interface_name_is_valid(3)— check if a string is a valid bus name or object path — is it valid? check it ✅sd_bus_is_anonymous(3)— set or query properties of a bus object — is it anonymous? anonymous vibes 🕶️
...and we're still deep in the S's bestie, no cap, this is the biggest letter of the whole alphabet and it's giving main character energy 💅
the sd_bus_is_* girlies (yes they're all one family) 🫶
sd_bus_is_bus_client(3)— configure connection mode for a bus objectsd_bus_is_monitor(3)— configure connection mode for a bus objectsd_bus_is_open(3)— check whether the bus connection is open or readysd_bus_is_ready(3)— check whether the bus connection is open or readysd_bus_is_server(3)— configure connection mode for a bus objectsd_bus_is_trusted(3)— set or query properties of a bus object
matchmaking + name checks 🌸
sd_bus_list_names(3)— retrieve info about the registered names on a bussd_bus_match_signal(3)— add a match rule for incoming message dispatchingsd_bus_match_signal_async(3)— add a match rule for incoming message dispatchingsd_bus_member_name_is_valid(3)— check if a string is a valid bus name or object path
the sd_bus_message_append* era ✨ (so many siblings omg)
sd_bus_message_append(3)— attach fields to a D-Bus message based on a type stringsd_bus_message_append_array(3)— append an array of fields to a D-Bus messagesd_bus_message_append_array_iovec(3)— append an array of fields to a D-Bus messagesd_bus_message_append_array_memfd(3)— append an array of fields to a D-Bus messagesd_bus_message_append_array_space(3)— append an array of fields to a D-Bus messagesd_bus_message_append_basic(3)— attach a single field to a messagesd_bus_message_append_string_iovec(3)— attach a string to a messagesd_bus_message_append_string_memfd(3)— attach a string to a messagesd_bus_message_append_string_space(3)— attach a string to a messagesd_bus_message_append_strv(3)— attach an array of strings to a messagesd_bus_message_appendv(3)— attach fields to a D-Bus message based on a type string
containers, copying, dumping 🎀
sd_bus_message_close_container(3)— create and move between containers in D-Bus messagessd_bus_message_copy(3)— copy the contents of one message to anothersd_bus_message_dump(3)— produce a string representation of a message for debugging purposessd_bus_message_enter_container(3)— create and move between containers in D-Bus messagessd_bus_message_exit_container(3)— create and move between containers in D-Bus messages
the sd_bus_message_get_* section, aka the longest glow-up in history 💜
sd_bus_message_get_allow_interactive_authorization(3)— set and query bus message metadatasd_bus_message_get_auto_start(3)— set and query bus message metadatasd_bus_message_get_bus(3)— create a new bus message object and create or destroy references to itsd_bus_message_get_cookie(3)— returns the transaction cookie of a messagesd_bus_message_get_creds(3)— query bus message addressing/credentials metadatasd_bus_message_get_destination(3)— set and query bus message addressing informationsd_bus_message_get_errno(3)— query bus message addressing/credentials metadatasd_bus_message_get_error(3)— query bus message addressing/credentials metadatasd_bus_message_get_expect_reply(3)— set and query bus message metadatasd_bus_message_get_interface(3)— set and query bus message addressing informationsd_bus_message_get_member(3)— set and query bus message addressing informationsd_bus_message_get_monotonic_usec(3)— retrieve the sender timestamps and sequence number of a messagesd_bus_message_get_path(3)— set and query bus message addressing informationsd_bus_message_get_realtime_usec(3)— retrieve the sender timestamps and sequence number of a messagesd_bus_message_get_reply_cookie(3)— returns the transaction cookie of a messagesd_bus_message_get_sender(3)— set and query bus message addressing informationsd_bus_message_get_seqnum(3)— retrieve the sender timestamps and sequence number of a messagesd_bus_message_get_signature(3)— query bus message signaturesd_bus_message_get_type(3)— query bus message addressing/credentials metadata
more sd_bus_message_* because the list literally never ends 😭
sd_bus_message_has_signature(3)— query bus message signaturesd_bus_message_is_empty(3)— query bus message signaturesd_bus_message_is_method_call(3)— query bus message addressing/credentials metadatasd_bus_message_is_method_error(3)— query bus message addressing/credentials metadatasd_bus_message_is_signal(3)— query bus message addressing/credentials metadataSD_BUS_MESSAGE_METHOD_CALL(3)— create a new bus message object and create or destroy references to itSD_BUS_MESSAGE_METHOD_ERROR(3)— create a new bus message object and create or destroy references to itSD_BUS_MESSAGE_METHOD_RETURN(3)— create a new bus message object and create or destroy references to itsd_bus_message_new(3)— create a new bus message object and create or destroy references to itsd_bus_message_new_method_call(3)— create a method call messagesd_bus_message_new_method_errno(3)— create an error reply for a method callsd_bus_message_new_method_errnof(3)— create an error reply for a method callsd_bus_message_new_method_error(3)— create an error reply for a method callsd_bus_message_new_method_errorf(3)— create an error reply for a method callsd_bus_message_new_method_return(3)— create a method call messagesd_bus_message_new_signal(3)— create a signal messagesd_bus_message_new_signal_to(3)— create a signal messagesd_bus_message_open_container(3)— create and move between containers in D-Bus messagessd_bus_message_peek_type(3)— read a sequence of values from a messagesd_bus_message_read(3)— read a sequence of values from a messagesd_bus_message_read_array(3)— access an array of elements in a messagesd_bus_message_read_basic(3)— read a basic type from a messagesd_bus_message_readv(3)— read a sequence of values from a messagesd_bus_message_ref(3)— create a new bus message object and create or destroy references to itsd_bus_message_rewind(3)— return to beginning of message or current containersd_bus_message_seal(3)— prepare a D-Bus message for transmissionsd_bus_message_send(3)— queue a D-Bus message for transfersd_bus_message_set_allow_interactive_authorization(3)— set and query bus message metadatasd_bus_message_set_auto_start(3)— set and query bus message metadatasd_bus_message_set_destination(3)— set and query bus message addressing informationsd_bus_message_set_expect_reply(3)— set and query bus message metadatasd_bus_message_set_sender(3)— set and query bus message addressing informationSD_BUS_MESSAGE_SIGNAL(3)— create a new bus message object and create or destroy references to itsd_bus_message_skip(3)— skip elements in a bus messagesd_bus_message_unref(3)— create a new bus message object and create or destroy references to itsd_bus_message_unrefp(3)— create a new bus message object and create or destroy references to itsd_bus_message_verify_type(3)— check if the message has specified type at the current location
macros babe, macros 💅
SD_BUS_METHOD(3)— declare properties and methods for a D-Bus pathSD_BUS_METHOD_WITH_NAMES(3)— declare properties and methods for a D-Bus pathSD_BUS_METHOD_WITH_NAMES_OFFSET(3)— declare properties and methods for a D-Bus pathSD_BUS_METHOD_WITH_OFFSET(3)— declare properties and methods for a D-Bus pathsd_bus_negotiate_creds(3)— control feature negotiation on bus connectionssd_bus_negotiate_fds(3)— control feature negotiation on bus connectionssd_bus_negotiate_timestamp(3)— control feature negotiation on bus connectionssd_bus_new(3)— create a new bus object and create or destroy references to itsd_bus_object_path_is_valid(3)— check if a string is a valid bus name or object path
the sd_bus_open_* squad, they all pull up together 🌈
sd_bus_open(3)— acquire a connection to a system or user bussd_bus_open_system(3)— acquire a connection to a system or user bussd_bus_open_system_machine(3)— acquire a connection to a system or user bussd_bus_open_system_remote(3)— acquire a connection to a system or user bussd_bus_open_system_with_description(3)— acquire a connection to a system or user bussd_bus_open_user(3)— acquire a connection to a system or user bussd_bus_open_user_machine(3)— acquire a connection to a system or user bussd_bus_open_user_with_description(3)— acquire a connection to a system or user bussd_bus_open_with_description(3)— acquire a connection to a system or user bus
path stuff + process 🔥
SD_BUS_PARAM(3)— declare properties and methods for a D-Bus pathsd_bus_path_decode(3)— convert an external identifier into an object path and backsd_bus_path_decode_many(3)— convert an external identifier into an object path and backsd_bus_path_encode(3)— convert an external identifier into an object path and backsd_bus_path_encode_many(3)— convert an external identifier into an object path and backsd_bus_process(3)— drive the connectionSD_BUS_PROPERTY(3)— declare properties and methods for a D-Bus path
creds, refs, names and replies 🦋
sd_bus_query_sender_creds(3)— query bus message sender credentials/privilegessd_bus_query_sender_privilege(3)— query bus message sender credentials/privilegessd_bus_ref(3)— create a new bus object and create or destroy references to itsd_bus_release_name(3)— request or release a well-known service name on a bussd_bus_release_name_async(3)— request or release a well-known service name on a bussd_bus_reply_method_errno(3)— reply with an error to a D-Bus method callsd_bus_reply_method_errnof(3)— reply with an error to a D-Bus method callsd_bus_reply_method_errnofv(3)— reply with an error to a D-Bus method callsd_bus_reply_method_error(3)— reply with an error to a D-Bus method callsd_bus_reply_method_errorf(3)— reply with an error to a D-Bus method callsd_bus_reply_method_errorfv(3)— reply with an error to a D-Bus method callsd_bus_reply_method_return(3)— reply to a D-Bus method callsd_bus_reply_method_returnv(3)— reply to a D-Bus method callsd_bus_request_name(3)— request or release a well-known service name on a bussd_bus_request_name_async(3)— request or release a well-known service name on a bussd_bus_send(3)— queue a D-Bus message for transfersd_bus_send_to(3)— queue a D-Bus message for transfersd_bus_service_name_is_valid(3)— check if a string is a valid bus name or object path
and the sd_bus_set_* girlies close us out 💖
sd_bus_set_address(3)— set or query the address of the bus connectionsd_bus_set_allow_interactive_authorization(3)— set or query properties of a bus objectsd_bus_set_anonymous(3)— set or query properties of a bus objectsd_bus_set_bus_client(3)— configure connection mode for a bus objectsd_bus_set_close_on_exit(3)— control whether to close the bus connection during the event loop exit phasesd_bus_set_connected_signal(3)— control emission of local connection establishment signal on bus connectionssd_bus_set_description(3)— sets or peeks at the properties of a bus object, no cap 💖sd_bus_set_exec(3)— sets or asks for the address your bus connection lives at ✨sd_bus_set_exit_on_disconnect(3)— decides what happens when the bus object disconnects — exit or vibe, your call 🦋sd_bus_set_fd(3)— hands over the file descriptors the bus uses to actually talk 🎀sd_bus_set_method_call_timeout(3)— sets or checks the default D-Bus method call timeout on a bus object ⏳🌸sd_bus_set_monitor(3)— flips the connection mode of a bus object, monitor girlie behavior 💅sd_bus_set_property(3)— sets or queries D-Bus service properties 👑sd_bus_set_propertyv(3)— same energy, same job: set or query D-Bus service properties, but thevone ✨sd_bus_set_sender(3)— picks the default sender for your outgoing messages, main character energy 📨sd_bus_set_server(3)— configures the connection mode of a bus object, server side 🫶sd_bus_set_trusted(3)— sets or queries the properties of a bus object, trust edition 🔥sd_bus_set_watch_bind(3)— controls the whole socket-binding-watching thing on bus connections 👀SD_BUS_SIGNAL(3)— declares properties and methods for a D-Bus path 🦋SD_BUS_SIGNAL_WITH_NAMES(3)— also declares properties and methods for a D-Bus path, but with names, iykyk ⭐sd_bus_slot_get_bus(3)— digs out info attached to a bus slot object 🌸sd_bus_slot_get_current_handler(3)— more info attached to a bus slot object, the handler one 🎀sd_bus_slot_get_current_message(3)— more info attached to a bus slot object, the current-message one 💌sd_bus_slot_get_current_userdata(3)— more info attached to a bus slot object, the current-userdata one 💜sd_bus_slot_get_description(3)— sets or queries the description of a bus slot object ✨sd_bus_slot_get_destroy_callback(3)— defines the callback function that handles resource cleanup 🧚sd_bus_slot_get_floating(3)— controls whether a bus slot object is "floating" (yes, floating, that's the term) 🎈sd_bus_slot_get_userdata(3)— sets and queries whatever's chilling in the"userdata"field 🍓sd_bus_slot_ref(3)— makes and destroys references to a bus slot object 💅sd_bus_slot_set_description(3)— sets or queries a bus slot object's description 🦋sd_bus_slot_set_destroy_callback(3)— defines the callback function for resource cleanup, setting edition 🎀sd_bus_slot_set_floating(3)— controls whether a bus slot object is "floating" 🌈sd_bus_slot_set_userdata(3)— sets and queries the value in the"userdata"field 👑sd_bus_slot_unref(3)— creates and destroys references to a bus slot object 🔥sd_bus_slot_unrefp(3)— creates and destroys references to a bus slot object, but thepvariant 💖sd_bus_start(3)— kicks off a bus connection to the D-bus broker daemon, let's gooo 🚀sd_bus_track_add_name(3)— adds, removes and retrieves bus peers tracked in a bus peer tracking object 💫sd_bus_track_add_sender(3)— adds, removes and retrieves tracked bus peers, sender flavor 📨sd_bus_track_contains(3)— adds, removes and retrieves tracked bus peers — this one checks who's in the group chat 👀sd_bus_track_count(3)— adds, removes and retrieves tracked bus peers, counting edition 🔢sd_bus_track_count_name(3)— adds, removes and retrieves tracked bus peers, counting by name 🏷️sd_bus_track_count_sender(3)— adds, removes and retrieves tracked bus peers, counting by sender 🧮sd_bus_track_first(3)— adds, removes and retrieves tracked bus peers, first one up 🌸sd_bus_track_get_bus(3)— tracks bus peers 💜sd_bus_track_get_destroy_callback(3)— defines the callback function for resource cleanup 🧹sd_bus_track_get_recursive(3)— tracks bus peers, recursively-ish 🌀sd_bus_track_get_userdata(3)— tracks bus peers, userdata edition 🍓sd_bus_track_new(3)— tracks bus peers, freshly made ✨sd_bus_track_next(3)— adds, removes and retrieves tracked bus peers, next up ⏭️sd_bus_track_ref(3)— tracks bus peers, ref style 🎀sd_bus_track_remove_name(3)— adds, removes and retrieves tracked bus peers, removal by name ✂️sd_bus_track_remove_sender(3)— adds, removes and retrieves tracked bus peers, removal by sender 🚫sd_bus_track_set_destroy_callback(3)— defines the callback function for resource cleanup, setting it this time 🧚sd_bus_track_set_recursive(3)— tracks bus peers, setting the recursive bit 👑sd_bus_track_set_userdata(3)— tracks bus peers, setting the userdata 🦋sd_bus_track_unref(3)— tracks bus peers, unreffing 💅sd_bus_track_unrefp(3)— tracks bus peers, unreffing with thep💖sd_bus_unref(3)— makes a new bus object and creates or destroys references to it 🔥sd_bus_unrefp(3)— makes a new bus object and creates or destroys references to it, thepone 🎀SD_BUS_VTABLE_CAPABILITY(3)— declares properties and methods for a D-Bus path ⭐SD_BUS_VTABLE_END(3)— declares properties and methods for a D-Bus path, and this one marks the end 🌈SD_BUS_VTABLE_START(3)— declares properties and methods for a D-Bus path, starting us off 🚀sd_bus_wait(3)— waits for I/O on a bus connection, patiently, like a good bestie ⏳SD_BUS_WRITABLE_PROPERTY(3)— declares properties and methods for a D-Bus path, writable girlie ✍️sd_device_ref(3)— creates or destroys references to a device object 💜sd_device_unref(3)— creates or destroys references to a device object, the destroy side 💀sd_device_unrefp(3)— creates or destroys references to a device object, with thep🌸sd_event(3)— acquires and releases an event loop object 🔄sd_event_add_child(3)— adds a child process state change event source to an event loop 👶sd_event_add_child_pidfd(3)— adds a child process state change event source to an event loop, pidfd flavor 🦋sd_event_add_defer(3)— adds static event sources to an event loop, deferred style ⏭️sd_event_add_exit(3)— adds static event sources to an event loop, exit style 🚪sd_event_add_inotify(3)— adds an "inotify" file system inode event source to an event loop 👀sd_event_add_inotify_fd(3)— adds an "inotify" file system inode event source to an event loop, fd edition 🎀sd_event_add_io(3)— adds an I/O event source to an event loop 💅sd_event_add_post(3)— adds static event sources to an event loop, post style 📮sd_event_add_signal(3)— adds a UNIX process signal event source to an event loop 📶sd_event_add_time(3)— adds a timer event source to an event loop ⏰sd_event_add_time_relative(3)— adds a timer event source to an event loop, relative timing 🕰️SD_EVENT_ARMED(3)— low-level event loop operations 🔧sd_event_child_handler_t(3)— adds a child process state change event source to an event loop 👶sd_event_default(3)— acquires and releases an event loop object, the default one ✨sd_event_destroy_t(3)— defines the callback function for resource cleanup 🧹sd_event_dispatch(3)— low-level event loop operations, dispatch vibes 📤sd_event_exit(3)— asks the event loop to please exit 🚪SD_EVENT_EXITING(3)— low-level event loop operations, exiting state 🏃SD_EVENT_FINISHED(3)— low-level event loop operations, finished state 🏁sd_event_get_exit_code(3)— asks the event loop to exit, and grabs the exit code on the way out 🔢sd_event_get_fd(3)— grabs a file descriptor you can poll for event loop events 👀sd_event_get_iteration(3)— low-level event loop operations, iteration edition 🔁sd_event_get_state(3)— low-level event loop operations, state edition 🧭sd_event_get_tid(3)— acquires and releases an event loop object, tid edition 🧵sd_event_get_watchdog(3)— enables event loop watchdog support 🐕sd_event_handler_t(3)— adds static event sources to an event loop 💅SD_EVENT_INITIAL(3)— low-level event loop operations, initial state 🌱sd_event_inotify_handler_t(3)— adds an "inotify" file system inode event source to an event loop 🦋sd_event_io_handler_t(3)— adds an I/O event source to an event loop 💖sd_event_loop(3)— runs an event loop 🔄sd_event_new(3)— acquires and releases an event loop object, new one 🎀sd_event_now(3)— retrieves the current event loop iteration timestamp ⏱️SD_EVENT_OFF(3)— enables or disables event sources, off state 🚫SD_EVENT_ON(3)— enables or disables event sources, on state ✅SD_EVENT_ONESHOT(3)— enables or disables event sources, one-shot style 🎯SD_EVENT_PENDING(3)— low-level event loop operations, pending state ⏳sd_event_prepare(3)— low-level event loop operations, prepare phase 🧰SD_EVENT_PREPARING(3)— low-level event loop operations, preparing state 🛠️SD_EVENT_PRIORITY_IDLE(3)— sets or retrieves the priority of event sources, idle priority 😴SD_EVENT_PRIORITY_IMPORTANT(3)— sets or retrieves the priority of event sources, important priority 🔥SD_EVENT_PRIORITY_NORMAL(3)— sets or retrieves the priority of event sources, normal priority 🌸sd_event_ref(3)— acquires and releases an event loop object, ref style 💜sd_event_run(3)— runs an event loop 🏃SD_EVENT_RUNNING(3)— low-level event loop operations, running state 🏃♀️sd_event_set_signal_exit(3)— automatically bails out of the event loop onSIGINTandSIGTERM🚪sd_event_set_watchdog(3)— enables event loop watchdog support 🐕sd_event_signal_handler_t(3)— adds a UNIX process signal event source to an event loop 📶SD_EVENT_SIGNAL_PROCMASK(3)— adds a UNIX process signal event source to an event loop, procmask edition 🎭sd_event_source(3)— adds an I/O event source to an event loop 💅sd_event_source_disable_unref(3)— bumps event source reference counters up or down 🔢sd_event_source_disable_unrefp(3)— bumps event source reference counters up or down, with thep✨sd_event_source_get_child_pid(3)— adds a child process state change event source to an event loop 👶sd_event_source_get_child_pidfd(3)— adds a child process state change event source to an event loop, pidfd style 🦋sd_event_source_get_child_pidfd_own(3)— adds a child process state change event source to an event loop, ownership edition 🎀sd_event_source_get_child_process_own(3)— adds a child process state change event source to an event loop, process-ownership edition 👑sd_event_source_get_description(3)— sets or retrieves the descriptive names of event sources 🏷️sd_event_source_get_destroy_callback(3)— defines the callback function for resource cleanup 🧹sd_event_source_get_enabled(3)— enables or disables event sources 🔘sd_event_source_get_event(3)— retrieves the event loop that an event source belongs to 🔄sd_event_source_get_floating(3)— sets or retrieves the 'floating' state of event sources 🎈sd_event_source_get_inotify_mask(3)— adds an "inotify" file system inode event source to an event loop 🎭sd_event_source_get_io_events(3)— adds an I/O event source to an event loop 💖sd_event_source_get_io_fd(3)— adds an I/O event source to an event loop, fd edition 🔌sd_event_source_get_io_fd_own(3)— adds an I/O event source to an event loop, fd-ownership edition 🫶sd_event_source_get_io_revents(3)— adds an I/O event source to an event loop, revents edition 🔁sd_event_source_get_pending(3)— figures out the pending state of event sources ⏳sd_event_source_get_priority(3)— sets or retrieves the priority of event sources 🔥sd_event_source_get_ratelimit(3)— configures rate limiting on event sources 🚦sd_event_source_get_signal(3)— adds a UNIX process signal event source to an event loop 📶sd_event_source_get_time(3)— adds a timer event source to an event loop ⏰sd_event_source_get_time_accuracy(3)— adds a timer event source to an event loop, accuracy edition 🎯sd_event_source_get_time_clock(3)— adds a timer event source to an event loop, clock edition 🕰️sd_event_source_get_userdata(3)— sets or retrieves the user data pointer of event sources 🍓sd_event_source_is_ratelimited(3)— configures rate limiting on event sources, and checks if you're being limited 🚦sd_event_source_leave_ratelimit(3)— configures rate limiting on event sources, and lets you leave it 🚪sd_event_source_ref(3)— bumps event source reference counters up or down 💜sd_event_source_send_child_signal(3)— adds a child process state change event source to an event loop 👶
okay bestie we are BACK and we are still in the S section, because the S section is enormous and honestly? it ate. buckle up. 🦋
sd_event_source_set_child_pidfd_own(3)— adds a child process state change event source to an event loop. yes "own", we see you, we appreciate you 💖sd_event_source_set_child_process_own(3)— also adds a child process state change event source to an event loop. same job, different queen 🧚sd_event_source_set_description(3)— sets or retrieves descriptive names of event sources. name your sources, they deserve it 🏷️sd_event_source_set_destroy_callback(3)— defines the callback function for resource cleanup. the "okay we're done here, tidy up" function 🧹sd_event_source_set_enabled(3)— enables or disables event sources. on/off, no in-between 👑sd_event_source_set_floating(3)— sets or retrieves the 'floating' state of event sources. it's giving no-strings-attached 💅sd_event_source_set_io_events(3)— adds an I/O event source to an event loop. 🍓sd_event_source_set_io_fd(3)— adds an I/O event source to an event loop. 💜sd_event_source_set_io_fd_own(3)— adds an I/O event source to an event loop. no cap. 🌸sd_event_source_set_prepare(3)— sets a preparation callback for event sources. prep before the main event, very backstage pass ✨sd_event_source_set_priority(3)— sets or retrieves the priority of event sources. main character ranking, fr 👑sd_event_source_set_ratelimit(3)— configures rate limiting on event sources. chill bestie, not so fast 🫶sd_event_source_set_ratelimit_expire_callback(3)— configures rate limiting on event sources. ⭐sd_event_source_set_time(3)— adds a timer event source to an event loop. ⏰sd_event_source_set_time_accuracy(3)— adds a timer event source to an event loop. 🎀sd_event_source_set_time_relative(3)— adds a timer event source to an event loop. 🌈sd_event_source_set_userdata(3)— sets or retrieves the user data pointer of event sources. your stuff, your pointer, your rules 💖sd_event_source_unref(3)— increases or decreases event source reference counters. 📉📈sd_event_source_unrefp(3)— increases or decreases event source reference counters. 💀sd_event_time_handler_t(3)— adds a timer event source to an event loop. 🦋sd_event_unref(3)— acquires and releases an event loop object. 🔄sd_event_unrefp(3)— acquires and releases an event loop object. ✨sd_event_wait(3)— low-level event loop operations. get low, get low, get low 💜
and now the getters, because elogind loves a getter, and honestly? same.
sd_get_machine_names(3)— determines available seats, sessions, logged in users and virtual machines/containers. 🖥️sd_get_seats(3)— determines available seats, sessions, logged in users and virtual machines/containers. 🪑sd_get_sessions(3)— determines available seats, sessions, logged in users and virtual machines/containers. yes, the whole list again, that's just how it is here 🧚sd_get_uids(3)— determines available seats, sessions, logged in users and virtual machines/containers. 👑
the 128-bit ID girlies. an ID icon, if you will 🆔
sd_id128_from_string(3)— formats or parses 128-bit IDs as strings. 🔢sd_id128_get_app_specific(3)— retrieves 128-bit IDs. 🌟sd_id128_get_boot(3)— retrieves 128-bit IDs. 🥾sd_id128_get_boot_app_specific(3)— retrieves 128-bit IDs. ✨sd_id128_get_invocation(3)— retrieves 128-bit IDs. 📞sd_id128_get_machine(3)— retrieves 128-bit IDs. 🤖sd_id128_get_machine_app_specific(3)— retrieves 128-bit IDs. 💅sd_id128_randomize(3)— generates 128-bit IDs. randomize era 🎲SD_ID128_STRING_MAX(3)— formats or parses 128-bit IDs as strings. 📏sd_id128_to_string(3)— formats or parses 128-bit IDs as strings. 🧵SD_ID128_TO_STRING(3)— formats or parses 128-bit IDs as strings. 🔤sd_id128_to_uuid_string(3)— formats or parses 128-bit IDs as strings. 🪪SD_ID128_TO_UUID_STRING(3)— formats or parses 128-bit IDs as strings. 📝SD_ID128_UUID_STRING_MAX(3)— formats or parses 128-bit IDs as strings. 📐
now we're checking file descriptors. vibe check but for fds 🔍
sd_is_fifo(3)— checks the type of a file descriptor. 🥤sd_is_mq(3)— checks the type of a file descriptor. 📬sd_is_socket(3)— checks the type of a file descriptor. 🔌sd_is_socket_inet(3)— checks the type of a file descriptor. 🌐sd_is_socket_sockaddr(3)— checks the type of a file descriptor. 📮sd_is_socket_unix(3)— checks the type of a file descriptor. 🐧sd_is_special(3)— checks the type of a file descriptor. not like other fds 💜
socket activation moment!! this is the good stuff 🔥
sd_listen_fds(3)— checks for file descriptors passed by the system manager. 🎁SD_LISTEN_FDS_START(3)— checks for file descriptors passed by the system manager. 🚩sd_listen_fds_with_names(3)— checks for file descriptors passed by the system manager. 🏷️
login monitors, aka the watching-the-whole-machine station 👀
sd_login_monitor(3)— monitors login sessions, seats, users and virtual machines/containers. 🛰️sd_login_monitor_flush(3)— monitors login sessions, seats, users and virtual machines/containers. 🚰sd_login_monitor_get_events(3)— monitors login sessions, seats, users and virtual machines/containers. 📅sd_login_monitor_get_fd(3)— monitors login sessions, seats, users and virtual machines/containers. 🧷sd_login_monitor_get_timeout(3)— monitors login sessions, seats, users and virtual machines/containers. ⏳sd_login_monitor_new(3)— monitors login sessions, seats, users and virtual machines/containers. 🆕sd_login_monitor_unref(3)— monitors login sessions, seats, users and virtual machines/containers. 🗑️sd_login_monitor_unrefp(3)— monitors login sessions, seats, users and virtual machines/containers. 🧼
VM/container class + network interface indices. nerd shit, lovingly 🧠
sd_machine_get_class(3)— determines the class and network interface indices of a locally running virtual machine or container. 🏫sd_machine_get_ifindices(3)— determines the class and network interface indices of a locally running virtual machine or container. 🔢
the notify girlies. hey bestie, i'm ready 💖
sd_notify(3)— notifies the service manager about start-up completion and other service status changes. 📣sd_notify_barrier(3)— notifies the service manager about start-up completion and other service status changes. 🚧sd_notifyf(3)— notifies the service manager about start-up completion and other service status changes. 🖨️
and now, the big one: who does this PID or socket peer actually belong to? genuinely one of the longest descriptions in this entire index, and every single one of these shares it, so here it is in full, again and again, exactly as promised:
determine the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to
sd_peer_get_cgroup(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🧬sd_peer_get_owner_uid(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 👤sd_peer_get_session(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🪑sd_peer_get_slice(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🍰sd_peer_get_user_slice(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🧁sd_pid_get_cgroup(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🧬sd_pid_get_owner_uid(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 👤sd_pid_get_session(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🪑sd_pid_get_slice(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🍰sd_pid_get_user_slice(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🧁
more notify, but make it pid-flavored 📣
sd_pid_notify(3)— notifies the service manager about start-up completion and other service status changes. 💌sd_pid_notify_barrier(3)— notifies the service manager about start-up completion and other service status changes. 🚧sd_pid_notify_with_fds(3)— notifies the service manager about start-up completion and other service status changes. 📎sd_pid_notifyf(3)— notifies the service manager about start-up completion and other service status changes. 🖨️sd_pid_notifyf_with_fds(3)— notifies the service manager about start-up completion and other service status changes. 📎🖨️
pidfd era. the glow-up of PID lookups tbh 🌟
sd_pidfd_get_cgroup(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🧬sd_pidfd_get_machine_name(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🏷️sd_pidfd_get_owner_uid(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 👤sd_pidfd_get_session(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🪑sd_pidfd_get_slice(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🍰sd_pidfd_get_unit(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🧱sd_pidfd_get_user_slice(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🧁sd_pidfd_get_user_unit(3)— determines the owner uid of the user unit or session, or the session, user unit, system unit, container/VM or slice that a specific PID or socket peer belongs to. 🏠
seat state check-in. is the seat okay? is it thriving? 🪑
sd_seat_can_graphical(3)— determines the state of a specific seat. 🖼️sd_seat_can_tty(3)— determines the state of a specific seat. ⌨️sd_seat_get_active(3)— determines the state of a specific seat. 🟢sd_seat_get_sessions(3)— determines the state of a specific seat. 🧑🤝🧑
and the session state girlies, all seventeen of them, no we are not skipping any, every single one is here and every single one determines the state of a specific session 💅
sd_session_get_class(3)— determines the state of a specific session. 🏷️sd_session_get_desktop(3)— determines the state of a specific session. 🖥️sd_session_get_display(3)— determines the state of a specific session. 🪟sd_session_get_leader(3)— determines the state of a specific session. 👑sd_session_get_remote_host(3)— determines the state of a specific session. 🌍sd_session_get_remote_user(3)— determines the state of a specific session. 🧑💻sd_session_get_seat(3)— determines the state of a specific session. 🪑sd_session_get_service(3)— determines the state of a specific session. 🛠️sd_session_get_start_time(3)— determines the state of a specific session. ⏱️sd_session_get_state(3)— determines the state of a specific session. 📊sd_session_get_tty(3)— determines the state of a specific session. ⌨️sd_session_get_type(3)— determines the state of a specific session. 🔠sd_session_get_uid(3)— determines the state of a specific session. 🆔sd_session_get_username(3)— determines the state of a specific session. 🙋sd_session_get_vt(3)— determines the state of a specific session. 🖥️sd_session_is_active(3)— determines the state of a specific session. 🟢sd_session_is_remote(3)— determines the state of a specific session. 📡
and finally (for this part, anyway), the uid girls, checking in on your login state 💜
sd_uid_get_display(3)— determines the login state of a specific Unix user ID. 🪟sd_uid_get_login_time(3)— determines the login state of a specific Unix user ID. 🕰️sd_uid_get_seats(3)— figure out the login state of one specific Unix user ID 🫶sd_uid_get_sessions(3)— same energy, also checking the login state of a specific Unix user ID ✨sd_uid_get_state(3)— bestie, it's the login state of a specific Unix user ID again 💅sd_uid_is_on_seat(3)— yes, this one too: determine the login state of a specific Unix user ID 🎀sd_watchdog_enabled(3)— checks whether the service manager is expecting watchdog keep-alive notifications from a service 👀 lowkey important, don't ghost itsleep.conf(5)— the suspend and hibernation configuration file 🌙sleep.conf.d(5)— also the suspend and hibernation configuration file, but the directory drop-in version 💤
✨ SEE ALSO ✨
elogind.directives(7)— go read this one next, fr fr 💖
Okay so this index is huge — it contains 539 entries, referring to 134 individual manual pages. That's not a vibe check, that's a whole personality. 🌈
And that's the whole page, bestie — you made it to the end and you absolutely ate. 💅✨
This was elogind version 255, page ELOGIND.INDEX(7), and yes the source and version info is doing its little footer thing down there like always. 🦋 Mwah, go read a real page now. 👑
📦 where this page comes from
- debian trixie: elogind 255.17-1debian2 · LGPL-2.1-or-later
- 💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms