SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Please let fuser in rc.6 check that the given directory is really a mountpoint:
Code:
echo "Killing processes holding NFS mount $dir open..."
# Background this to prevent fuser from also blocking shutdown:
/usr/bin/fuser -k -M -m $dir &
For some yet unknown reason i still had an entry of an already unmounted NFS volume in /etc/mtab (which is what /bin/mount is listing) which resulted in fuser killing everything still accessing the root partition so that the reboot failed with INIT: no more processes left in this runlevel.
Code:
-m NAME, --mount NAME
NAME specifies a file on a mounted file system or a block device
that is mounted. All processes accessing files on that file
system are listed. If a directory file is specified, it is
automatically changed to NAME/. to use any file system that
might be mounted on that directory.
-M, --ismountpoint
Request will be fulfilled only if NAME specifies a mountpoint.
This is an invaluable seatbelt which prevents you from killing
the machine if NAME happens to not be a filesystem.
Last edited by Markus Wiesner; 12-28-2017 at 04:09 PM.
Reason: typo
+ver 5.48:
+ Fix issue with subscriptions for unpaired devices.
+ Fix issue with handling A2DP and no available SEP.
+ Fix issue with handling AVCTP change path support.
+ Fix issue with handling AVCTP browsing channel.
+ Fix issue with handling AVCTP passthrough PDUs.
+ Fix issue with handling detaching of controller.
+ Fix issue with handling start discovery results.
+ Fix issue with handling non-connectable devices.
+ Fix issue with handling unused parameter in WriteValue.
+ Add support for service side AcquireWrite and AcquireNotify.
+ Add support for providing address type information.
+ Add support for cable based authentication and pairing.
+ Add support for Bluetooth Low-Energy battery service.
+ Add support for BTP client for qualification testing.
+ Add support for additional Mesh control functionality.
+ Mark advertising manager APIs as stable interfaces.
Please let fuser in rc.6 check that the given directory is really a mountpoint:
Code:
echo "Killing processes holding NFS mount $dir open..."
# Background this to prevent fuser from also blocking shutdown:
/usr/bin/fuser -k -M -m $dir &
For some yet unknown reason i still had an entry of an already unmounted NFS volume in /etc/mtab (which is what /bin/mount is listing) which resulted in fuser killing everything still accessing the root partition so that the reboot failed with INIT: no more precesses left in this runlevel.
Code:
-m NAME, --mount NAME
NAME specifies a file on a mounted file system or a block device
that is mounted. All processes accessing files on that file
system are listed. If a directory file is specified, it is
automatically changed to NAME/. to use any file system that
might be mounted on that directory.
-M, --ismountpoint
Request will be fulfilled only if NAME specifies a mountpoint.
This is an invaluable seatbelt which prevents you from killing
the machine if NAME happens to not be a filesystem.
Good catch - I've had that happen sporadically on a couple of (unimportant) machines here and never bothered to figure out what was causing it; both of the machines are old, so I (wrongly?) assumed it was just age-related.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
