Next: Internals
Up: Error Messages
Previous: Error Messages
- Server seems to be already running
Despite of the message, the real cause is simply the existance of the
fifo
used
for communication with the clients. It is created when the server
starts and removed if it terminates in a ``civilized'' fashion (upon a
fatal error that is recognized or via a signal handler). If a signal
that is not catched occurres or when the system goes down without the
proper shutdown procedure, this fifo may still exist although the
server is not running. In this case just remove the fifo:
rm /tmp/automountd.fifo
- Cannot create fifo, server may already be running
This is the same as the preceding item.
- Cannot open fifo
No special points to watch, should not occurr.
- malloc() failed
The system has maybe limited resources. Normally the daemon should use
about 50k of system memory.
- calloc() failed
See previous entry.
- buffersize exceeded
Although a simple message, it indicates that something is seriously
wrong: A read() returned more characters than the buffer provided
could hold. One possible way to produce this kind of error is to use
device names longer than about 255 characters. Should not occurr.
- fseek() failed
There is a failure during access to the initialization file. Should
not occurr.
- Initialization error
Something went wrong during startup. Usually this error message will
not appear, as the error will in most cases be recognized and reported
at an earlier time.
- Init file error
There was an error reading the init file. Normally the error will be
reported at an earlier time with additional information.
- Internal error (bad mount() values)
Some arguments that have been checked for correctness are rejected by
the mount() system call. Check the configuration file. See
section 2.4.
- effective UID is not root
When the daemon is started by a normal user, the first mount attempt
will fail with this error message. The daemon is normally started at
boot time with superuser privileges. The 'eject' client is used by
normal users. For testing purposes see section 5.3.
- Unknown error (bad errno)
This indicates an unexpected errno value after the call to mount().
- realloc() failed
The dynamic size change of internal tables failed. This can happen
due to memory limitations or by specifying an abnormal number of
devices in the config file. See section 5.2 for a possible
solution. Note: This is not a program failure. Theoretically the
server can handle several thousands of devices contained in config
file lines with unlimited length.
- Config file (...) not found
The config file could not be found. Make sure that it exists.
Every error message text that is completely surrounded by parentheses
such as (Internal Error) is a really fatal error. This will only
occurr when the compiler failed or something like that. In this case
try to recompile and maybe change the optimization level.
Next: Internals
Up: Error Messages
Previous: Error Messages
Fri Sep 25 18:04:42 GMT 1998