Dangerous rm -rf command Post: 302937732

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

List of dangerous Unix command

Hi Guys, I wonder if one of you would have a list of dangerous commands on unix. Regards

2. SuSE

inconsistent ls command display at the command prompt & running as a cron job

Sir, I using the following commands in a file (part of a bigger script): #!/bin/bash cd /opt/oracle/bin ls -lt | tail -1 | awk '{print $6}' >> /tmp/ramb.out If I run this from the command prompt the result is: 2007-05-16 if I run it as a cron job then...

3. HP-UX

Upgrade serviceguard can be "dangerous"?

Hi everybody! We have to upgrade serviceguard 11.14 to 11.16, so I get PHSS_36898 patch from HP. Is it necessary to uninstall serviceguard 11.14 before install this patch? (I think so, but i am not sure). Do you know if is "dangerous" this kind of upgrade? Any suggestions about? Thx in...

4. Shell Programming and Scripting

assign a command line argument and a unix command to awk variables

Hi , I have a piece of code ...wherein I need to assign the following ... 1) A command line argument to a variable e.g origCount=ARGV 2) A unix command to a variable e.g result=`wc -l testFile.txt` in my awk shell script When I do this : print "origCount" origCount --> I get the...

5. AIX

AIX:Command to get netaddress/subnet address command in IPv4/IP6

AIX:Command to get netaddress/subnet address command in IPv4/IP6 Can anybody help us with a command to retrieve netaddress/subnet address command in IPv4/IP6 on aix machine. net/subnet address is in the format 172.16.212.0(signifies all 255 machines in an IPv4 network)

6. Linux

Is umount -l dangerous?

I had a umount busy issue, that the usual fuser -mk did not solve, I did a umount -l and was able to unmount the device, I then got in trouble by the storage team staff: Here was a snippet of their response: Using "umount -l" is a potentially dangerous act. The command combination for a lazy...

7. Shell Programming and Scripting

Need help! command working ok when executed in command line, but fails when run inside a script!

Hi everyone, when executing this command in unix: echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error. here is content of my script: tdbsrvr$ vi hc.sh "hc.sh" 22 lines, 509...

8. Shell Programming and Scripting

List of dangerous shell commands

Hello, I have a Application which needs to run shell scripts in a elevated state (root) for system interrogation. So I execute each script using bash -C. This has worked really well. I now want to add another layer of security, I cant inspect each of the scripts before they get deployed to the...

9. UNIX for Dummies Questions & Answers

passing command output from one command to the next command in cshell

HI Guys, I hope you are well. I am trying to write a script that gets executed every time i open a shell (cshell). I have two questions about that 1) I need to enter these commands $ echo $DISPLAY $ setenv $DISPLAY output_of_echo_$display_command How can i write a...

LEARN ABOUT DEBIAN

cmannotifyd

cmannotifyd(8)						     CMAN Notification Daemon						    cmannotifyd(8)

NAME

       cmannotifyd - CMAN Notification Daemon

SYNOPSIS

       cmannotifyd [-f] [-d]

DESCRIPTION

       The cmannotifyd daemon talks to CMAN and provides a mechanism to notify external entities about cluster changes.

       CMAN dispatches 3 kind of notifications:

       - CMAN_REASON_TRY_SHUTDOWN when cman requests to all clients if it is allowed to shutdown.

       - CMAN_REASON_STATECHANGE when cman detects a node joining or leaving the cluster.

       - CMAN_REASON_CONFIG_UPDATE when a configuration change event has been detected/requested.

       These notifications are then dispatched to the shell script cman_notify in the environment variable CMAN_NOTIFICATION.

       cman_notify will then execute all the scripts in the configured notification directory (default: /etc/cluster/cman-notify.d) passing a very
       minimal set of envvars including, of course, the CMAN_NOTIFICATION= type.  The execution order is set by the filename as shown by "LC_ALL=C
       ls -las".

       cmannotifyd logs are stored in the default log file (/var/log/cluster/cmannotifyd.log).

       cman_notify  logs are stored in the default log file (/var/log/cluster/cman_notify.log). By default the output from the scripts executed by
       cman_notify is redirected to /dev/null.	Users can either set CMAN_NOTIFICATION_DEBUG=1 in their environment or set proper debug configura-
       tion in cluster.conf to redirect scripts output to the cman_notify log file.

NOTES

       cmannotifyd does not block on cman_notify nor check the exit status of the script.

       Notifications are dispatched in the same order as they arrive, one by one.

       CMAN_REASON_TRY_SHUTDOWN  is  passed  to  scripts  for information only, they can not influence cman's decsion about whether or not to shut
       down.

       CMAN_REASON_STATECHANGE also implies CMAN_NOTIFICATION_QUORUM exported in the environment. CMAN_NOTIFICATION_QUORUM will be set to 1  (when
       the node is part of a quorate cluster) or 0 (otherwise).

       A template for cman_notify scripts can be found in the doc/ directory.

OPTIONS

       -f     Run in the foreground (do not fork / daemonize).

       -d     Enable debug output.

								   November 2008						    cmannotifyd(8)