- Some resources related to Sharity-Light
- /usr/local/share/doc/Sharity-Light/README (http://ibiblio.org/pub/Linux/system/filesystems/smbfs/Sharity-Light.1.0.README)
- Pantz.org site about OpenBSD and Server Message Block mounts
- Blog EShell
- Install Sharity-Light
- Installing Sharity-Light in OpenBSD
Don't see your OS here? Consider checking additional resources:
If the resource is password protected, place the password in a text file. (This approach assumes trust of any system administrator who could access this file. This is generally considered to be more secure than specifying the password on a command line.)
- Making the file
Make sure the destination directory exists:
The name of the server must be in the /etc/hosts file. (Or maybe lmhosts, alternatively? Some further research/testing/investigatino may be warranted.)
It is currently believed that the name does not matter: it can be anything; it just needs to be something. However, the IP address needs to be accurate. (The IP address needs to accurately be pointing at the SMB server.)
Then, here is a basic sample command line:
Depending on what is intended, you might want to leave off the
Additional command line parameters that may be useful include:
-D0xff to enable debugging, or “
-W ” to specify a different workgroup.
which will show a “device” that was mounted. That “device” includes the PID. Then use
. Then, after that works and the mount no longer shows up when running
, send a SIGTERM (via
, not a SIGKILL from “
”) to the PID of the related
process. Then the PID should nicely disappear.
Variations of this, like using
before a successful
, has been known to cause undesirable behavior like
freezing up, the mount point remaining, a “
” messsage, and so forth. (Not recommended.)
nfs server shlight-
PID##: not responding
- Automatically starting Sharity-Light
Compared to many other servers, Sharity-Light may be a bit tougher to get to usefully mount automatically when a computer is started.
Currently some info/background/discussion at:
Have the startup script run the terminal multiplexer. For example, in OpenBSD:
Then, configure the specified “terminal multiplexer” configuration file.
The following example tends to keep commands short, by referring to other script(s) as needed. That way, if there is (eventually) a desire to run multiple commands, this may get slightly complicated, simply by listing those commands, instead of getting very complicated because it contains all of the complexity of the commands.
new -d -s
Then, finally, in the referenced files, place the Sharity-Light commands.