Strange behavior with tar Post: 302897854

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

strange sed behavior

I have a file called products.kp which contains, for example, 12345678,1^M 87654321,2^M 13579123,3 when I run the command cat products.kp| sed -f kp.sed where kp.sed contains s,^M,, I get the output 12345678,1 87654321,2 13579123,3

2. Shell Programming and Scripting

nawk strange behavior

Dear guys; when deleting repeated lines using nawk as below ; Why the below syntax works? nawk ' !a++' infile > outfile and when using the other below syntax the nawk doesn't work? nawk ' { !a++ } ' infile > outfile or nawk ' { !a++ } ' infile > outfile BR

3. Programming

Strange behavior in C++

I have the following program: int main(int argc, char** argv){ unsigned long int mean=0; for(int i=1;i<10;i++){ mean+=poisson(12); cout<<mean<<endl; } cout<<"Sum of poisson: "<< mean; return 0; } when I run it, I get the...

4. Ubuntu

Ubuntu strange behavior

It is so till login screen. I mean that when I boot my computer, Ubuntu shows a splash screen with mouse instead of Ubuntu logo and in the login screen it shows XUbuntu login screen... It began when I upgraded to previous kernel, I suppose, but I'm not sure... I can't say that it annoys me very...

5. Red Hat

strange mail behavior

Hi I have script to to take backup and send mail to a group once a day. One strange behavior I have observed recently is that most of the time the mail we receive is fine . But someday it just sends out mail without any subject with undisclosed recipients. I dont know how to find the cause...

6. AIX

Strange memory behavior

Hello together, i have a strange memory behavior on a AIX 7.1 System, which i cannot explain. The Filesystem-Cache will not be grow up and drops often after few minutes. I know if a file was deleted, that the same segment in the FS-Cache will also be cleared. But i am not sure if this is the...

7. Shell Programming and Scripting

Strange behavior on one of my server

I am not sure what is wrong, but I have some strange behavior when printing things out. I do create a file with only one word test, no space, no new line etc. nano file<enter> test<ctrl x>y<enter> Server 1 gets (fail) awk '{print "+"$0"*"}' file *test Server 2 gets (OK) awk '{print...

8. Shell Programming and Scripting

Strange behavior of grep

Hi All, I am facing a strange problem while grepping for a process. Here is the small script that i have written. It will look for any process running with the parameter passed to the script. If no process is running it should print appropriate message. $ cat t.ksh #!/bin/ksh set -x ...

9. Shell Programming and Scripting

Strange Ctrl+C behavior

Hello All, I have a strange issue. I've created a shell script which connects to RMAN (Oracle Recovery Manager) and executes full DB backup. I then executed this script with nohup and in the background: $ nohup my_script.sh > logfile.log 2>&1 &The issue is that when I tried to take a look into...

LEARN ABOUT DEBIAN

wdmd

WDMD(8) 						      System Manager's Manual							   WDMD(8)

NAME

       wdmd - watchdog multiplexing daemon

SYNOPSIS

       wdmd [OPTIONS]

DESCRIPTION

       This  daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done.  Every test interval
       (10 seconds), the daemon tests each source.  If any test fails, the KEEPALIVE is not done.  In a standard configuration, the watchdog timer
       will  reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout").	This means that if single test fails 5-6 times in row, the
       watchdog will fire and reset the system.  With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.

       T seconds, P pass, F fail
       T00: test1 P, test2 P, test3 P: KEEPALIVE done
       T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
       T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
       T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
       T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
       T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
       T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
       T60: watchdog fires, system resets

       (Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)

       A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog	is
       guaranteed  to fire, regardless of whether other sources on the system have passed or failed.  A spurious reset due to the combined effects
       of multiple failing tests as shown above, is an accepted side effect.

       wdmd will exit if a watchdog driver is not loaded.

       wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).

   Test Source: clients
       Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
       Every test interval, wdmd will check if the expiry time for a connection has been reached.  If so, the test for that client fails.

       (Other test sources such as scripts executed each test interval may be added in the future.)

OPTIONS

       -D     Enable debugging to stderr and don't fork.

       -H num Enable (1) or disable (0) high priority features such as realtime scheduling priority and mlockall.
	      Default 1.

								    2011-08-01								   WDMD(8)