|
|
Sponsored Content
Operating Systems
Solaris
unable to open a .log(4MB) file in vi
Post 302147698 by raman1605 on Wednesday 28th of November 2007 04:35:36 AM
11-28-2007
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How, where from and which UNIX or LINUX can I download so that I can use it normally working on 386 SX 4MB RAM.
I want to use only its basic functions and C and C++ compiler on it.
I need it for my studies.
P.S I need a stable UNIX or LINUX including a full set of
functions of C... (4 Replies)
Discussion started by: Traiancho
4 Replies
2. UNIX for Advanced & Expert Users
I am trying to build a tuxedo server which in turn depends on several Pro*C programs. I am doing it on HP-UX system.
It looks to me that the ORACLE_HOME is set properly.
But I am getting error message when trying to build.
PCC-F-NOERRFILE, unable to open error message file, facility PR2
exit... (1 Reply)
Discussion started by: asutoshch
1 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
We are running Oracle 8.1.7 on HP-UX B.11.00. Recently we have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script we use has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out .
However we receive the error
SP2-0310: unable to open file... (2 Replies)
Discussion started by: guru_2007
2 Replies
4. UNIX for Dummies Questions & Answers
Hi ,
I am running Oracle 8.1.7 on HP-UX B.11.00. Recently I have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out .
However I receive the error
SP2-0310: unable to open file... (2 Replies)
Discussion started by: Ananth.p
2 Replies
5. AIX
Hi All,
Can't find any documentation on the web for this anywhere, except about three web pages that are in Chinese.
When I enter SMIT on this box, I get
ERROR MESSAGE: Unable to open temp file
I suspected smit.log, but it is universal readable, writeable by root, and I am root.... (6 Replies)
Discussion started by: jeffpas
6 Replies
6. UNIX for Advanced & Expert Users
I am working on a unix server.
I killed all the processes with my id on the machine.
After that I tried to delete a file, I got an error:-
file not removed.Text File busy.
Deletion of directory prompted:-
Directory not empty.
Can anyone help me regarding this...???
Thanks,
Vikas (11 Replies)
Discussion started by: vikasrout
11 Replies
7. Shell Programming and Scripting
Hi,
I was compiling few C programs in the unix server and getting the following error message
rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent
proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE
INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE ... (1 Reply)
Discussion started by: kavithakuttyk
1 Replies
8. Red Hat
Hi,
I am unable to create/open any file in vi editor for normal user, though using root I am able to create/open any file, using redhat 5.5,
example
vi test
it showing nothing after entering command (9 Replies)
Discussion started by: manoj.solaris
9 Replies
9. Shell Programming and Scripting
Not able to open a file using this code
why not?
use strict;
use warnings;
my $file = "verInfo.txt";
unless(open FILE, $file) {
# Die with error message
# if we can't open it.
die "\nUnable to open $file\n";
}
my $line = <FILE>;
print $line;
close FILE; (7 Replies)
Discussion started by: srijith
7 Replies
10. UNIX for Beginners Questions & Answers
Hi,
Getting the below error while installing from ks.cfg unable to open input kickstart file curl#37 Couldn't open file /tmp/swappart
Here am trying to include /tmp/swappart file from pre section under disks and partition section. Dont know where exactly am doing wrong
My kickstart file... (3 Replies)
Discussion started by: Sumanthsv
3 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)