02-06-2009
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message.
Error: Internal system error: Unable to initialize standard output file
I'm guessing more info might be needed, so let me know.
Thanks (2 Replies)
Discussion started by: firkus
2 Replies
2. UNIX for Advanced & Expert Users
HI,
I have a file which comes from crystal reports in the below format.
I need to clean the file so that i will only have the columns(deptid,empid,ename,sal) and the data below the column names.
There is a bug in the repoting tool( we only see page1-1 for every department).The rundate change... (1 Reply)
Discussion started by: kris01752
1 Replies
3. UNIX for Advanced & Expert Users
BeginDate 07/01/06
End: 07/31/06
Cust: A02991 - Burnham
0002000 5,829,773 145.3
0009701 4,043,850 267.3
2005000 286,785.13 100.0
BeginDate 07/01/06
End: 07/31/06
Cust: A01239 - East Track PSE
Index A
0009902 317,356.82 890.2
0020021 ... (5 Replies)
Discussion started by: kris01752
5 Replies
4. HP-UX
Background:
# uname -a
HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license
deedee.rsn.hp.com:/
# bdf /opt
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol6 6553600 6394216 158144 98% /opt
/opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies
5. Solaris
Hi,
The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB.
The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space.
ofcourse the software... (31 Replies)
Discussion started by: iris1
31 Replies
6. AIX
F7FA22C9 I O SYSJ2 UNABLE TO ALLOCATE SPACE IN FILE SYSTEM
edit by bakunin: until you are willing to phrase a decent question i am unwilling to tolerate such a spammed thread here.
- Thread closed - (0 Replies)
Discussion started by: ranjithm
0 Replies
7. Solaris
Hi
I have the following cenario:
I have requested a LUN from the NetApp to create a file system, and the netapp admin provide me with one as you can see below, but after following all the steps, I could not create a file system on the device:
# format
Searching for disks...done
... (11 Replies)
Discussion started by: fretagi
11 Replies
8. Red Hat
Hi
I have the following difficulty:
the NetApp admin has clone one file system from one red hatserver and presented this cloned LUN into another redhat server.
I can see the LUN as:
fdisk -l
Disk /dev/sda: 64.4 GB, 64424509440 bytes
255 heads, 63 sectors/track, 7832 cylinders
Units =... (1 Reply)
Discussion started by: fretagi
1 Replies
9. AIX
Hi,
I have inherited this AIX 5.3 host. I'm unable to increase the /usr file system. It gives me this error.
What needs to be done to remove this error?
vios:/home/padmin$ chfs -a size=+128M /usr
0516-304 lquerypv: Unable to find device id 0002ef4df616f9690000000000000000 in the Device
... (14 Replies)
Discussion started by: dn888
14 Replies
LEARN ABOUT OPENDARWIN
ipl
IPL(4) Kernel Interfaces Manual IPL(4)
NAME
ipl - IP packet log device
DESCRIPTION
The ipl pseudo device's purpose is to provide an easy way to gather packet headers of packets you wish to log. If a packet header is to be
logged, the entire header is logged (including any IP options - TCP/UDP options are not included when it calculates header size) or not at
all. The packet contents is also logged after the header.
Prepending every packet header logged is a structure containing information relevant to the packet following and why it was logged. The
structure's format is as follows:
struct ipl_ci {
u_long sec; /* time when the packet was logged */
u_long usec;
u_long plen; /* length of packet data logged */
u_short hlen; /* length of headers logged */
u_short rule; /* rule number (for log ...) or 0 if result = log */
u_long flags:24; /* XXX FIXME do we care about the extra bytes? */
#if (defined(OpenBSD) && (OpenBSD <= 1991011) && (OpenBSD >= 199606))
u_long filler:8; /* XXX FIXME do we care? */
u_char ifname[IFNAMSIZ];
#else
u_long unit:8;
u_char ifname[4];
#endif
};
In the case of the header causing the buffer to finish on a non-32bit
boundary, padding will be `appended' to ensure that the next log entry
is aligned to a 32bit boundary.
If the packet contents is more then 128 bytes, then only 128 bytes of the
packet contents is logged. Should the packet contents finish on a non-32bit
boundary, then the last few bytes are not logged to ensure the log entry
is aligned to a 32bit boundary.
ipl is a read-only (sequential) character pseudo-device.
The ioctls which are loaded with this device can be found under ipf(4).
The only ioctl which is used for logging and doesn't affect the filter is:
ioctl(fd, SIOCIPFFB, int *)
This ioctl flushes the log buffer and returns the number of bytes flushed.
There is currently no support for non-blocking IO with this device, meaning all read operations should be considered blocking in nature (if
there is no data to read, it will sleep until some is made available).
SEE ALSO
ipf(4)
BUGS
Packet headers are dropped when the internal buffer (static size) fills.
FILES
/dev/ipl0
IPL(4)