Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Date command to obtain the last month is not working correctly.. Post 302392020 by tigersk on Wednesday 3rd of February 2010 06:56:20 AM
Old 02-03-2010
I have Redhat ES 4.5
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Script not working correctly

I have a simple script that I want to run every 30 minutes but only when I execute it. I don't want it to be a crontab job. so i have for example date ls -l who sleep 1800 The first time it executes correctly but after the first time it nevers execute back again. It should execute after... (2 Replies)
Discussion started by: elchalateco
2 Replies

2. Shell Programming and Scripting

if not working correctly

Anyone have an idea why this if statement does not work correctly? "test2.sh" 18 lines, 386 characters #!/usr/bin/sh WARNING=80 CRITICAL=95 check_it() { if ] || ];then echo "YES ] || ]" else echo "NO ] || ]" fi } check_it 80.1 check_it 81.1 (3 Replies)
Discussion started by: 2dumb
3 Replies

3. Shell Programming and Scripting

Use date command to find last month

#!/usr/bin/ksh Does anyone have a good way to set a variable to last month? For example, today is 20070810. I would like to use the date command to set a variable to last months %m code, which is 07. If I pluck this months value (08) and user expr to do simple math on it, it returns 7 (not... (5 Replies)
Discussion started by: Cbish68
5 Replies

4. UNIX for Dummies Questions & Answers

print previous month (current month minus 1) with Solaris date and ksh

Hi folks month=`date +%m`gives current month Howto print previous month (current month minus 1) with Solaris date and ksh (7 Replies)
Discussion started by: slashdotweenie
7 Replies

5. Shell Programming and Scripting

how to obtain date and day of the week from `date` command

Hi, does anybody know how to format `date` command correctly to return the day of the week? Thanks -A I work in ksh.... (1 Reply)
Discussion started by: aoussenko
1 Replies

6. Shell Programming and Scripting

rsync is not correctly working

We are using Red Hat linux system. I am transferring my rman backup files to another server. Here is the command i am using to transfer the files. /usr/bin/rsync -avpP --delete /xyz/xyz/ 99.99.999.99::db110bkp Here is the rsync version. >rsync --version rsync version 3.0.6 ... (1 Reply)
Discussion started by: govindts
1 Replies

7. Shell Programming and Scripting

date command not working

hi #!usr/bin/perl -w local ($date) = `/sbin/date "+%D %X" ` ; print $date when i run this in ksh shell it is giving the below error sh: /sbin/date: not found but same code is working and displaying date and time in sh shell. what could be the reason. pls help (10 Replies)
Discussion started by: psthariharan
10 Replies

8. UNIX for Dummies Questions & Answers

date command - getting previous month

Hi, On any given day, I want to capture the month that has gone by - said otherwise, how do I capture last month? expr date '+%m' - 1 Above expression is giving error. Please advise thanks ---------- Post updated at 09:28 AM ---------- Previous update was at 09:11 AM... (1 Reply)
Discussion started by: ab_2010
1 Replies

9. Shell Programming and Scripting

Help with getting last date of previous month and first date of previous 4th month from current date

I have requirment to get last date of previous month and the first date of previous 4th month: Example: Current date: 20130320 (yyyymmdd) Last date of previous month: 20130228 (yyyymmdd) First date of previous 4th month: 20121101 (yyyymmdd) In my shell --date, -d, -v switches are not... (3 Replies)
Discussion started by: machomaddy
3 Replies

10. Shell Programming and Scripting

Obtain date for first Tuesday of every month

Hi , Please help me out to write a shell script to obtain the date of first tueday of every month. I am new to shell scripting. Appreciate your help Thanks. (7 Replies)
Discussion started by: prongs22
7 Replies
PROOFD(1)						      General Commands Manual							 PROOFD(1)

NAME
proofd - PROOF (The Parallel ROOT Facility) DESCRIPTION
Using PROOF (The Parallel ROOT Facility) one can analyze trees in parallel on a cluster of computers. The PROOF system consists of the proofd(1) from-end program which is started via inetd(8). proofd takes care of user authentication and overlays itself then with the desired version of the proofserv(1) executable. The proofserv(1) is a basically the same as the ROOT interactive module root(1), except that it reads its commands from a socket instead of from the terminal. Since it is a remote server it will not do graphics and therefore is not linked with any graphics libraries (Motif, X11, etc.). SETTING UP PROOF
Since you need to handle sensitive system files, you need to have root (the user, not the program!) privileges. Also, it's recommended that you read the appropriate man(1) pages first. These are inetd(8) (the internet daemon), sysklogd(8) and syslog(3) (the system logger dae- mon), and init(8) (the SYSV process control initializer). In other words: Be very VERY carefull when installing proofd There, I said it. And ofcourse, no warrenties what so ever. 1 Make sure every node has ROOT installed. We'll assume you installed the ROOT applications in <bindir> (e.g. /usr/bin) and the PROOF configuration files in files in <proofdir>/etc (e.g. /usr/share/root/etc). 2 The TCP port 1094 was allocated by IANA, ( www.iana.org <Iwww.iana.org> ), to rootd, so add to /etc/services the lines: proofd 1093/tcp rootd 1094/tcp 3 On each node, add to /etc/inetd.conf the lines: proofd stream tcp nowait root <bindir>/proofd proofd <proofdir>/proof rootd stream tcp nowait root <bindir>/rootd rootd -i You can substitute the <proofdir> with any directory that holds your PROOF configuration, for example /etc/root/proof. However, it should be shared among all nodes in the cluster. 4 Restart inetd or force it to re-read the config file: kill -1 <inetd pid> If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/inetd restart or whatever is appropriate for your system. 5 On the master node, add to /etc/syslog.conf the line: local5,local6.debug <proofdir>/log/proof.log and all slave nodes: local5,local6.debug @<master hostname> where <master hostname> is domain name of the master node. All PROOF syslog messages will be collected on the master node. Just make one node in the cluster the master, all others are slaves. 6 On all nodes, change the below lines in /etc/syslog.conf, *.info;mail.none;news.none;authpriv.none /var/log/messages to: *.info;local5,local6,mail.none;news.none;authpriv.none /var/log/messages 7 Create an empty <proofdir>/log/proof.log: echo "" > <proofdir>/log/proof.log 8 Restart syslogd or force it to re-read the config file: kill -1 <syslogd pid>. If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/sysklogd restart or whatever is appropriate for your system. 9 Edit <proofdir>/etc/proof.conf to reflect your cluster configuration. See the example proof.conf file for more information. If you installed ROOT using some precompiled package (for example a Redhat Linux or a Debian GNU/Linux package), steps 2 to 4 may already be done for you. If you're running Linux, Steps 5 to 7 can be somewhat automated using the script proof-facility in <proofdir> of your distribution. This script uses syslog-facility(1), from the Linux syslog(1) distribution, and may run on other platforms as well - but no warrenties mind you! Step 9 is completely up to the user. EXAMPLE
That's it. To test PROOF try the following: root [1] gROOT->Proof("<master hostname>") root [2] gPROOF->Print() <shows information on the master and all active slave servers> root [3] .q FILES
<proofdir> The location of your PROOF data. In binary packages, like for Redhat LinuxI or Debian GNU/Linux, this will probably be /usr/share/root/proof. If you got a binary tar(1)-ball from the ROOT website, or a build it yourself without the static paths option, then this directory could be ROOTSYS/proof. However, you may set it to something else when starting your server. <proofdir>/etc This directory holds all the configuration files for your cluster(s). <proofdir>/etc/<cluster>.conf This is the cluster named <cluster> configuration file. See <proofdir>/etc/<cluster>.conf.sample for an example. <proofdir>/etc/motd This is Message-Of-The-Day file. See <proofdir>/etc/motd.sample for an example. <proofdir>/etc/noproof If this file is present, all PROOF services will be diabled. See <proofdir>/etc/noproof.sample for an example. <proofdir>/etc/proof.conf This is the PROOF configuration file. See <proofdir>/etc/proof.conf.sample for an example. ~/.rootnetrc.conf Configuration file for network access. Here you specify login names and pass word, so it MUST be read/write-able only by the user. See <proofdir>/etc/rootnetrc.conf.sample for an example. <proofdir>/log This directory holds the log files from the master and slaves. <proofdir>/log/proof.log Syslog(1) log file for PROOF. SEE ALSO
proofserv(1) , root(1) , rootd(1) More information can be found at the ROOT website: http://root.cern.ch <http://root.cern.ch> ORIGINAL AUTHORS
The ROOT team (see web page above): Rene Brun and Fons Rademakers COPYRIGHT
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as pub- lished by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foun- dation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA AUTHOR
This manual page was written by Christian Holm Christensen <cholm@nbi.dk>, for the Debian GNU/Linux system (but may be used by others). ROOT
Version 3 PROOFD(1)
All times are GMT -4. The time now is 03:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy