02-05-2012
Stop your syslog daemon.
Delete the /dev/log using rm, then restart the syslog daemon.
That should create socket /dev/log
Regards
Peasant.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi, I am trying to write 2 simple scripts. One to echo a message into a socket, and the other to read from it. There are many tutorials about, but they're mostly about retrieving web pages through a socket. The code I'm trying is
echo qwerty > /dev/udp/localhost/22 (the first port I found that... (2 Replies)
Discussion started by: zeppelin147
2 Replies
2. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
3. Shell Programming and Scripting
Hi
i am running oracle database import through a script and script scans the import log to see if there are any errors.
Now the porblem is that when i run the script the import log appears on the screen even if i direct the output of import to /dev/null.
imp "'/ as sysdba'"... (5 Replies)
Discussion started by: vinoo128
5 Replies
4. UNIX for Advanced & Expert Users
Hi,
I was porting ipv4 application to ipv6; i was done with TCP transports. Now i am facing problem with SCTp transport at runtime.
To test SCTP transport I am using following server and client socket programs. Server program runs fine, but client program fails giving Invalid Arguments for... (0 Replies)
Discussion started by: chandrutiptur
0 Replies
5. UNIX for Advanced & Expert Users
Hi ,
when a process fails to write to /dev/log ? (1 Reply)
Discussion started by: Gopi Krishna P
1 Replies
6. IP Networking
I need clarification on whether it is okay to set socket options on a listening socket
simultaneously when it is being used in an accept() call?
Following is the scenario:-
-- Task 1 - is executing in a loop - polling a listen socket, lets call it 'fd', (whose file descriptor is global)... (2 Replies)
Discussion started by: jake24
2 Replies
7. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
8. AIX
Hello AIXians,
I can't boot my AIX, it hangs and stops at the code error: 0518
After searching google, I knew the problem is due to problems in File Systems.
So the solution is booting from any bootable media, then run these commands in maintenance mode:
#fsck -y /dev/hd4
#fsck -y... (3 Replies)
Discussion started by: Mohannad
3 Replies
9. Shell Programming and Scripting
Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc
How would I parse the below information and initialize variables
(an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions?
Something along the lines of:
sgdisk -n... (12 Replies)
Discussion started by: RogerBaran
12 Replies
10. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
LEARN ABOUT REDHAT
xchklog
xchklog(8) JFS utility - extract fsck.jfs log xchklog(8)
NAME
xchklog - extract a log from the JFS fsck workspace into a file
SYNOPSIS
xchklog [ -f output.file ] [ -p ] [ -V ] device
DESCRIPTION
xchklog extracts the contents of either the most recent or immediately prior JFS fsck service log from the specified device, and writes the
output into a specified or default file. (The default file name is <pwd>fscklog.new. If the -p option is used, the default file name is
<pwd>fscklog.old.)
The contents of the output file can be formatted into text by using the JFS utility xchkdmp.
device is the special file name corresponding to the actual device from which the fsck log will be extracted (e.g. /dev/hdb1 ).
OPTIONS
-f output.file
Specify the output file name, overriding the default file name.
output.file must be 127 characters or less in length.
output.file will be created in the present working directory unless it is fully qualified.
-p Extract the prior log (as opposed to the most recent log).
-V Print version information and exit (regardless of any other chosen options).
EXAMPLES
Extract the most recent log on /dev/hda5 into <pwd>fscklog.new:
xchklog /dev/hda5
Extract the most recent log on /dev/hdb3 into /temp/l9651107.log:
xchklog -f /temp/l9651107.log /dev/hdb3
Extract the prior log on /dev/hdb4 into <pwd>fscklog.old:
xchklog -p /dev/hdb4
REPORTING BUGS
If you find a bug in JFS or xchklog, please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site:
http://oss.software.ibm.com/jfs
Please send as much pertinent information as possible, including any xchklog error messages and the complete output of running fsck.jfs
with the -v option on the JFS device.
SEE ALSO
xchkdmp(8), mkfs.jfs(8), fsck.jfs(8), logdump(8), logredo(8), xpeek(8)
AUTHOR
Barry Arndt (barndt@us.ibm.com)
xchklog is maintained by IBM.
See the JFS project web site for more details:
http://oss.software.ibm.com/jfs
January 11, 2002 xchklog(8)