LOCKFS-NOTIFY(1)
π LOCKFS-NOTIFY π
okay bestie, welcome to the lockfs-notify manual page, from the User Commands girlies π
this one's short, sweet, and honestly kind of iconic. let's get into it π¦
β¨ NAME β¨
lockfs-notify β bestie, this is the lil cutie that notifies you about temporary or permanent changes on fs π
β¨ SYNOPSIS β¨
lockfs-notify [-a|--always|-l|--lockfs|-n|--nolockfs] [-t TIME|--expire-time=TIME]
lockfs-notify -h|--help
β¨ DESCRIPTION β¨
so like, lockfs-notify is a wrapper around notify-send(1). that's the whole vibe. it's the middleman, the bestie who delivers the message π¬
what does it actually do tho? it sends a notification to users at the beginning of a session, telling them whether temporary or permanent changes are allowed on which filesystems β or, to be more precise (periodt π ), on which mountpoints.
β¨ OPTIONS β¨
okay so real talk first: if you invoke several of the -a, -l or -n options (or their long forms, respectively --always, --lockfs or --nolockfs), the last one overrides the previous ones. last one standing wins, no cap π
also β invoking any of these options overrides the variable BILIBOP_LOCKFS_NOTIFY_POLICY that can be set in bilibop.conf(5). so yeah, command line said what it said π£οΈ
-a,--alwaysβ always send a notification bestie!! π it'll tell you about filesystems on which permanent changes are allowed, AND about filesystems on which temporary changes are allowed. so if thebilibop-lockfsfeature is enabled, and one or more mountpoints have been whitelisted in/etc/bilibop/bilibop.conf, then two notifications are send to the user. two!! double the slay β¨-h,--helpβ prints a short help message on stdout and dips. short king behavior π-l,--lockfsβ send a notification only about filesystems for which thelockfsfeature has been enabled, i.e. about mountpoints for which only temporary changes are allowed. and bestieβ¦ all these changes will be lost at next shutdown of the computer π gone. poof. make your peace with it π-n,--nolockfsβ send a notification only about filesystems for which thelockfsfeature has been disabled, i.e. about mountpoints for which permanent changes are allowed. these changes will be kept after the shutdown of the computer π«Ά they live on, main character energy fr fr-t TIME,--expire-time=TIMEβ specifies the timeout in milliseconds at which to expire the notification β° so here's the tea: values of TIME less than1000(1 second) make the timeout disabled and the notification never expires β it's immortal, it's giving forever β¨ and if TIME is not an integer, this option is silently ignored. no error, no drama, just ignored π
β¨ FILES β¨
/etc/xdg/autostart/lockfs-notify.desktopβ the one file. the whole file list. she's alone but she's thriving πΈ
β¨ SEE ALSO β¨
go read these too bestie, they're all connected iykyk π₯
β¨ AUTHOR β¨
this manual page has been written by Bilibop Project <quidame@poivron.org> π«Ά absolute legend, ty for your service
and that's the whole page bestie!! π this was bilibop, dated 2012-05-22, and it ate, no crumbs left π
β¨ periodt π
π¦ where this page comes from
- debian bookworm: bilibop-lockfs 0.6.3 Β· GPL-3.0-or-later
- debian trixie: bilibop-lockfs 0.6.5 Β· GPL-3.0-or-later
- ubuntu jammy: bilibop-lockfs 0.6.3 Β· GPL-3.0-or-later
- ubuntu noble: bilibop-lockfs 0.6.3 Β· GPL-3.0-or-later
- ubuntu resolute: bilibop-lockfs 0.6.5 Β· GPL-3.0-or-later
- ubuntu stonking: bilibop-lockfs 0.6.5 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms