Search Results

${x} should be enclosed in quotes. but it's also because you have special characters in the string like "[" and "]". Why do you have to such a long (exact) search string?

That's because $x is treated as a regex, seeing "[ACTIVE]" as bracket expression for one single character.
Use the fixed string option -F to grep.

Show us your attempts so far. Did you consider the citations/links at the bottom of this page?
Did you consider modifying the date output format?

sample autosys jil

/*************MY_JOB_1***********/

insert_job: MY_JOB_1 job_type: c
command: /full-path-of-/clean.sh <dirname>
machine: your-machine-name
owner: owner-of-the-script...

only one script is enough. But you need 7 different autosys job. (If you want to clean the directories in different time).

If you want to clean all the directories in a particular time, then one...

o/p "5" is the yesterday's date.. both the syntax in "if" condition are having mild difference. just a additional space is included in "grep" command .. if the date value is less than 10, then while...

try this ..

#!/bin/bash
yest_dat_mon=`TZ=CST+24 date +%b`
yest_dat_day=`TZ=CST+24 date +%d | sed 's,^0,,g'`
if [ "$yest_dat_day" -lt 10 ]
then
ls -ltr|grep " $yest_dat_mon ...

If you don't have root access, you can't, but have to ask the SA to implement it.

Maybe in this adapted form:[ $( id -g ) -eq 641 ] && alias rm="rm -i"
That way it would only apply to your group,...

alias rm='rm -i'
Add it to Your /etc/profile

Well... Yes. But it's better use some more descriptive names (usually in uppercase) and export them. Add something like this in your profile:
APACHE_N=`...`
export APACHE_N
But these values will...

Maybe something like this, give it a try:

#!/usr/bin/ksh
/usr/ucb/ps auxww | grep 10[9]9 |grep rmi

if [ $? -eq 0 ]
then
pid = `/usr/ucb/ps auxww | grep 10[9]9 |grep rmi| awk '{print $2}'`...

awk '/01\/Aug/,/02\/Aug/ { print } ' input


Regards
Peasant.

There should be no non-interactive passing of passwords to ssh - that's what keys are for. Passing passwords always means to have them unencrypted in your filesystem. You could do it though with...

Please try to use this :

history | awk '$1~/72/{print $0}'

history 800 | grep 391?

Actually, it should be:

find . -name '*.cer' -exec bash -c '
fn=$1
keytool -v -list -printcert -file "$fn" |
fgrep -i "Aug 03" &&
printf "%s\n" "$fn"
' inline {} \;

If it...