hi guys,
need some help on this error message.
im running solaris 2.6 on a e3500 and lately i encountered this error:-
lp: Warning: Received SIGPIPE; continuing
last message repeated 1 time
Multiple Softerrors:
2 Intermittent, 4 Persistent, and 0 Sticky Softerrors accumulated
from... (4 Replies)
Hello experts,
I have installed solaris 10 on x86. When I try to boot I get an error
with ablue screen
login failed please try again. I am new to this o.s. It used to work
nicely before what did I do wrong?
Any guidance advice will be highly appreciated
Thanks, (5 Replies)
Hi All,
while building, i am receiving the following error......
Undefined first referenced
symbol in file
void os_directory::create(const std::string &) obj.release/BOConfig.o (symbol belongs to implicit dependency... (2 Replies)
Hi All,
please help me about filesystem error on sun fire 245 sparc solaris 10, i have installed solaris 10 os on sun fire 245 and done with mirroring disk.
but after reboot the server i having this error below shown by system :
checking ufs filesystems
/dev/md/rdsk/d60: is logging.... (4 Replies)
I have compiled my application on Solaris 10 with following description
SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25
But when installing the application on Solaris 9
SunOS odcarch02 5.9... (2 Replies)
When in the terminal on Solaris 10 this terminal error keeps popping up and won't stop, how do I remove it?
Nov 24 13:22:42 unknown sendmail: unable to qualify my own domain name (unknown) -- using short name
Nov 24 13:22:42 unknown sendmail: oAOIMgqg017431: SYSERR(root): fill_fd:... (6 Replies)
Hello Everyone,
I was able to successfully compile cracklib and pam_cracklib. But when I use it in /etc/pam.conf it fails to work.
Error on CLI:
# passwd testuser
Unexpected failure. Password file/table unchanged.
Error in /var/adm/messages:
Mar 30 7:14:27 solaris10 passwd: dlsym... (1 Reply)
Hi,
I am using solris 8 and i am unable to start my tomcat. I am getting the below error.
Error occurred during initialization of VM
Unable to load native library: ld.so.1: java: fatal: libscf.so.1: open failed: No such file or directory
Please let me know. (1 Reply)
I cannot solve the following error bellow.
Can someone help me on this please?
Mar 31 07:08:45 serverx sudo: fork
Mar 31 07:18:50 serverx sudo: fork
Mar 31 07:28:45 serverx sudo: fork
Mar 31 07:38:47 serverx sudo: fork
Mar 31 07:48:45 serverx sudo: fork
Mar 31 07:58:45 serverx... (1 Reply)
Discussion started by: pangarano
1 Replies
LEARN ABOUT OSF1
log
log(8) System Manager's Manual log(8)NAME
log - Records input and output from a program
SYNOPSIS
/usr/sbin/log <logfile> <command>
OPERANDS
The file in which to record the interaction being logged. The command to execute.
DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until
<command> exits, the log program exits, and the exit status of <command> is returned.
The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and
/var/adm/smlogs/it.log installation log files.
RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation.
The log program does not search for the PATH variable to locate <command> and error messages are terse.
The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands
will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will
not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log
foo.tmp /sbin/sh -i
In the previous example, foo.tmp is the name of <logfile>.
The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must
exit by some other means.
ERRORS
Log open error
Explanation:
The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.
Exec Error
Explanation:
The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe-
cutable file.
Fork Error
Explanation:
The log program was unable to create one of the processes it requires to log data.
SEE ALSO
Commands: it(8), script(1)log(8)