Dump syntax used with autoloader
This message results from the superuser attempting to unmount a filesystem that is not mounted. Subdirectories of filesystems, such as /var, cannot be unmounted.
Run the mount(1M) or df(1M) command to see what filesystems are mounted. If you really want to unmount one of them, specify the existing mount point.
User receives the following error message. The only thing that had changed was the IP address of the machine.
The IP address defined with ifconfig(1M) must match that in /etc/hosts. That is, if you change the machine's IP address with ifconfig(1M) you must also change the machine's entry in the /etc/hosts file.
For machines with multiple interfaces, you must check and possibly update /etc/hostname.*.
When trying to bring up a Terminal window (dtterm) in CDE, a popup appears stating: Unable to get pty!.
This error is because dtterm is not able to open /dev/pts/int (where int is an integer). The reason they cannot open this file is grantpt(3C) failed to change the permissions on the file. grantpt(3C) failed because the binary /usr/lib/pt_chmod is not setuid root. The permissions on /usr/lib/pt_chmod must be 4111.
To restore the correct permissions to pt_chmod, use the following command: (as root)
# chmod 4111 /usr/lib/pt_chmod |
These messages appear in /var/adm/messages at boot time, when the system tries to load drivers for devices the machine does not have.
Despite the alarmist tone, this message is intended as only informational. You probably don't want all these device drivers, because they make your system kernel larger, requiring more memory.
While trying to open the graphical recovery interface by running nwrecover from the client, the error was displayed.
In this case, multiple networker servers existed and nwrecover could not determine which network server to use for the client.
The server can be specified to the nwrecover command with the -s option.
nwrecover -c client_name -s server_name |
Error is as follows: uname: error writing name when booting System cannot bootstrap.
Boot off CD-ROM and check /etc/nodename. The file must contain exactly one line with the name of the system. No blank, or other, lines are allowed.
This message, prefaced by the file name and line number involved, is from the C preprocessor /usr/ccs/lib/cpp, and indicates a line starting with a sharp (#) but not followed by a valid keyword such as define or include.
A piece of software might be running the C preprocessor on an initialization file that you thought was interpreted by a shell. In most shells, the sharp (#) indicates a comment. The C preprocessor considers comments to be anything between /* and */ delimiters.
This message from the C shell csh(1) indicates that a user typed a command containing a backquote symbol (`) without a closing backquote. Similar messages result from an unmatched single quote (') or an unmatched double quote ("). Other shells generally give a continuation prompt when a command line contains an unmatched quote symbol.
Correct the command line and try again. To continue typing on another line, give the C shell a backslash right before the newline.
During phase 4, fsck(1M) discovered that the specified file was orphaned because the inode had no record of its pathname. In other words, the file was not connected with any directory.
Answer yes to reconnect the file into the lost+found directory. Then contact the file's owner to ask if you should send it back, and where to place it.
For more information, see the chapter on checking filesystem integrity in the System Administration Guide, Volume I.
This C shell message might come as a surprise to Bourne or Korn shell users accustomed to logging out with a Control-d.
When ignoreeof is set, the C shell requires users to logout by typing logout(1) or exit(1). Write any modified files to disk before exiting.
When trying to mail to a user, the error Username... User unknown is displayed. The user is on the same system.
Check for typo the entered e-mail address. Or, the user could be aliased to a non-existant e-mail address in /etc/mail/aliases or the user's .mailrc file.
You cannot mail to a user that has capital letters in its name. sendmail(1M) converts all the capital letters to lowercase before attempting to find the user. Since UNIX is case sensitive, it finds no username on the system with all lowercase letters, so it displays the User unknown message.
Workaround: Make sure all usernames are composed of *only* lowercase letters.
While running CDE, the error in the console or /var/adm/messages file:
Oct 19 04:41:00 darkcastle last message repeated 393 times Oct 19 04:41:01 darkcastle inetd[120]: /usr/dt/bin/rpc.ttdbserverd:Child Status Changed |
The fix is to create the following soft links:
ln -s /usr/openwin/bin/rpc.ttdbserver /usr/dt/bin/rpc.ttdbserver ln -s /usr/openwin/bin/rpc.ttdbserverd /usr/dt/bin/rpc.ttdbserverd |
This means that the xinit(1) program, which sets up X11 resources and starts a window manager, failed to locate the X server process. Perhaps the user interrupted window system startup, or exited abnormally from OpenWindows (for example, by killing processes or by rebooting). It is possible that the X server crashed. Data loss is possible in some cases. Depending on process timing, this message might be normal when OpenWindows exits during a system reboot.
The only solution is to exit and restart OpenWindows. You do not need to reboot the system unless it hangs and fails to give you a console prompt. To exit OpenWindows, select Workspace->Exit. To restart OpenWindows, type openwin(1) at the system prompt.
When compiling some code for BSD compatibility the error happened after invoking usr/ucb/cc. The unbundled compiler (SPARCworks Professional C product) was installed in /opt.
/usr/ucb/cc is a script which checks for the file /usr/ccs/bin/ucbcc and, if found, invokes it with appropriate library flags for BSD-compatibility compilation.
/usr/ucb/cc is part of the package SUNWscpu. /usr/ccs/bin/ucbcc is supposed to be a symbolic link to /opt/SUNWspro/bin/acc, which is created during installation of the unbundled C compiler, SPROcc.
Verify that you have the essential OS-bundled Developer packages, SUNWscpu, SUNWbtool, and the unbundled C compiler:- SPROcc. However, /usr/ccs/bin/ucbcc was missing on customer's system. Evidently somewhere along the line this link was removed.
Solve the problem by creating a new symbolic link:
# ln -s /opt/SUNWspro/bin/acc /usr/ccs/bin/ucbcc |
Commands used to identify which packages contain particular components involved:
craterlake% grep ucb/cc /var/sadm/install/contents /usr/ucb/cc f none 0555 bin bin 3084 50323 814621113 *SUNWscpu craterlake% ls -l /usr/ucb/cc -r-xr-xr-x 1 bin bin 3084 Oct 25 1995 /usr/ucb/cc craterlake% file !$ file /usr/ucb/cc /usr/ucb/cc: executable /usr/bin/sh script craterlake% grep ucbcc /var/sadm/install/contents /usr/ccs/bin/ucbcc=/opt1/40/SUNWspro/SC4.0/bin/acc s none SPROcc SPROcc.2 SPROcc.5 craterlake% file /usr/ccs/bin/ucbcc /usr/ccs/bin/ucbcc: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, stripped craterlake% ls -l /usr/ccs/bin/ucbcc lrwxrwxrwx 1 root other 31 Aug 23 1996 /usr/ccs/bin/ucbcc -> /opt1/40/SUNWspro/SC4.0/bin/acc |
When using userdel to delete a user:
userdel -r userid |
Free up space on root (/) filesystem.