fs-cifs umount ?

fs-cifs seems to work on limited testing. My question is what is
the proper method to unmount the remote drive.

umount

gives an error:

umount /MS-C/

Attempting to umount: /MS-C/
umount(/MS-C/) failed: No such device or address

slaying fs-cifs seems to work, but is a poor alternative to umount. If
for example, one has several remote drives mounted from several windows
machines and you want to turn off one machine, then you’d have to
figure out which instance of fs-cifs to terminate. It would be better to be able to umount that drive(s)


\

David L. Hawley D.L. Hawley and Associates

I agree that slaying fs-cifs isn’t exactly the most elegant solution, but its the only way now that I know
of. Just make sure you use a different instance of fs-cifs for each mount, and use “pidin arg | grep
{CIFS-Name}” to easily get the PID to slay.

I’ve asked this before, and I figure the sqeaky wheel gets the grease, so how about QSSL adds capability to
fs-cifs to prompt the user for the CIFS password if not specified on the command-line? I really hate the
lack of security when I have to type in and its echoed to the screen.

Jim

David Hawley wrote:

fs-cifs seems to work on limited testing. My question is what is
the proper method to unmount the remote drive.

umount <cifs MS windows drive

gives an error:

umount /MS-C/

Attempting to umount: /MS-C/
umount(/MS-C/) failed: No such device or address

slaying fs-cifs seems to work, but is a poor alternative to umount. If
for example, one has several remote drives mounted from several windows
machines and you want to turn off one machine, then you’d have to
figure out which instance of fs-cifs to terminate. It would be better to be able to umount that drive(s)


David L. Hawley D.L. Hawley and Associates

Jim Bormann a écrit :

I agree that slaying fs-cifs isn’t exactly the most elegant solution, but its the only way now that I know
of. Just make sure you use a different instance of fs-cifs for each mount, and use “pidin arg | grep
{CIFS-Name}” to easily get the PID to slay.

I’ve asked this before, and I figure the sqeaky wheel gets the grease, so how about QSSL adds capability to
fs-cifs to prompt the user for the CIFS password if not specified on the command-line? I really hate the
lack of security when I have to type in and its echoed to the screen.

Jim

David Hawley wrote:

fs-cifs seems to work on limited testing. My question is what is
the proper method to unmount the remote drive.

umount <cifs MS windows drive

gives an error:

umount /MS-C/

Attempting to umount: /MS-C/
umount(/MS-C/) failed: No such device or address

slaying fs-cifs seems to work, but is a poor alternative to umount. If
for example, one has several remote drives mounted from several windows
machines and you want to turn off one machine, then you’d have to
figure out which instance of fs-cifs to terminate. It would be better to be able to umount that drive(s)


David L. Hawley D.L. Hawley and Associates

I don’t know what the umount command do exactly, I suppose it send an appropriate message to a resource manager
so, I think that it shouldn’t be difficult for fs-cifs to unmount a device?

Alain.