Sponsored Content
Full Discussion: Is it a bug ..?
Top Forums Shell Programming and Scripting Is it a bug ..? Post 302214567 by vbe on Monday 14th of July 2008 09:36:01 AM
Old 07-14-2008
Looks more like someone is writing a log in /opt that fills the FS... or placed a temporary file that fills up /opt then removes the file or reduces it but it is not taken in account because the file is open...
 

8 More Discussions You Might Find Interesting

1. Programming

Bug has developed

Guys there is another bug that has developed.........now messaged above 6 bytes are trimmed and echoed back to client.After the first message the echo is not regular.I have put a loop in both client and server to check for closing.Moreover for connection close i also need to put another clause that... (3 Replies)
Discussion started by: arjunjag
3 Replies

2. Post Here to Contact Site Administrators and Moderators

Have I found a bug?

When searching for new posts, I see that my voting in one of the polls counts as a 'new post'. However, while the '<blah> minutes ago' entry updates correctly, the 'by <username>' is the last user to actually post a comment in the poll instead. Result: Poll: vB Guest Book 39... (4 Replies)
Discussion started by: Smiling Dragon
4 Replies

3. UNIX for Advanced & Expert Users

logrotate bug?

I have been mailing myself logs for a while, but just ran into a problem because of a process that cannot HUP its log. (I realize thats why they implemented the "copytruncate" option in the first place) When I use logrotate with "copytruncate" and "compress" there is a problem. The "myScript"... (0 Replies)
Discussion started by: jjinno
0 Replies

4. AIX

bug in 43 ???

xxxxserver# lsattr -El inet0 | grep 255.240.0.0,32.224.0.0,32.78.120.254 | grep '.40' route net,-hopcount,1,-netmask,255.240.0.0,32.224.0.0,32.78.120.254 How this is possible? (1 Reply)
Discussion started by: itik
1 Replies

5. UNIX for Dummies Questions & Answers

where's the bug?

#!/bin/bash if then #echo "infinite loop" exit 0 fi when I run this file I get the following error: ./test_infinite_loop: line 5: syntax error near unexpected token `fi' ./test_infinite_loop: line 5: `fi' :confused: (4 Replies)
Discussion started by: jon80
4 Replies

6. Programming

is this a bug of g++?

Hello, Im using the g++(g++ Ubuntu/Linaro 4.4.4-14ubuntu5 4.4.5) and im trying to compile a small snippet code and got into an endless loop.I recompiled that in VS2010 under Windows 7 and the answer is as expected.so i wonder is this a bug of g++?here is my code. #include<iostream> using... (5 Replies)
Discussion started by: homeboy
5 Replies

7. Shell Programming and Scripting

How to fix this bug?

Hi gurus, I have script as below: #!/bin/ksh while : do cat /dev/null > srcfile exit_time=`TZ=GMT-20 date +%Y%m%d1950` cur_time=`date +%Y%m%d%H%M` flag=1 if ; then ... (7 Replies)
Discussion started by: ken6503
7 Replies

8. UNIX for Advanced & Expert Users

A $(( expression )) bug?

This is for the big guns... I have been modifying AudioScope.sh to bring it inline with more current practices. I hit a bug which IS not present in the original code but was after modification. Shell check first:- #!/bin/sh txt="1234567890" echo "$(( $txt ))" echo "$(( ${#txt} - 1 ))" echo... (17 Replies)
Discussion started by: wisecracker
17 Replies
KSC(1)								   User Commands							    KSC(1)

NAME
ksc - Linux kernel module source checker SYNOPSIS
ksc [ -d | --directory ] DIRECTORY ksc [ -k | --ko ] FILE OPTIONS
KSC accepts command-line arguments, and has both a long and short form usage. You can use either style or combine them to specify options. When the tool is run with kernel module sources it checks for all four architectures, and when run with binary kernel modules, it checks for the specific architecture for which the binary was built. Valid RHEL whitelist releases are rhel6.0, rhel6.1, rhel6.2, rhel6.3, rhel6.4 -h, --help show this help message and exit -c CONFIG, --config=CONFIG path to the local ksc.conf file. If not specified the tool tries to read from ~/ksc.conf and if that is also not found then from /etc/ksc.conf -d DIRECTORY, --directory=DIRECTORY path to the directory -i, --internal to create text files to be used internally. -k KO, --ko=KO path to the ko file. You should either use -d or -k to run the KSC tool, but not both. If both -d and -k option is used at the same time then only -d is used and the -k option is discarded. -n RELEASENAME, --name=RELEASENAME Red Hat release against which the bug is to be filed. Default value is 6.5 -p PREVIOUS, --previous=PREVIOUS path to the previous resultset file and submit it as a bug to Red Hat Bugzilla. -r RELEASE, --release=RELEASE RHEL whitelist release used for comparison -s, --submit Submits the report to the Red Hat bugzilla (https://bugzilla.redhat.com). The credentials need to be in the /etc/ksc.conf file. The tool will prompt for bugzilla password. The configuration file looks like below: [bugzilla] user=user@redhat.com partner=partner-name partnergroup=partner-group server=https://bugzilla.redhat.com/xmlrpc.cgi -v, --version Prints KSC version number ksc - Version 0.9.11 Feb 2014 KSC(1)
All times are GMT -4. The time now is 03:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy