Hi,
I needed space on a FS, and when I've added the space on the filesystem, I did it trough the regular smitty fs inteface and not with smitty cl_lvm.
Can someone help me to repair the situat before a faileover happen ?
Thanks for your help,:mad: (13 Replies)
cat $1 | sort -n | uniq | $1
in other words, I sort the content of the file and put the ouput in the same file, is there any mistakes in this cshell code ??? (4 Replies)
hi,
instead of typing crontab -e i gave crontab -r and hit enter. So i lost all my scripts.
Is there any way to restore the deleted scripts?
Please help me out
Thanks
Ajay (3 Replies)
Hi everyone !
I have a file wich look like this :
>Sis01
> Sis02
...
>Sis44
I want to separe each paragraphe in a different file, so I decide to use the "FOR" loop + sed.
for f in {01..44}
do (5 Replies)
Hi,
I'm using fedora 15,
my defualt DE is XFCE I once saw that there is a option in startup DE's that I can select and it was OPENBOX. I just wanted to test it. but after choosing it as my DE here I am. I have just access to terminal, firefox.. what's in my desktop. there is no panel here. I... (0 Replies)
Hi there can anyone help me to spot my mistake and please explain why it appears
My code :
#!/usr/bin/gawk -f
BEGIN { bytes =0}
{ temp=$(grep "datafeed\.php" | cut -d" " -f8)
bytes += temp}
END { printf "Number of bytes: %d\n", bytes }
when I am running ./q411 an411
an411:
... (6 Replies)
Hi,
I want to start MY_PROGRAM in a bash script with additional parameters given in the CONFIGURATION_ARRAY.
IFS="'"
CONFIGURATION_ARRAY=( '-N 0 -m 0' '-N 0 -m 1' )
for configuration in ${CONFIGURATION_ARRAY}
do
//DEBUG
N=${configuration%-*} //-N 0
M=-${configuration##*-} //-m 0... (5 Replies)
#!/bin/bash
source=/to_be_archived
dest=/archived
echo "is this archive for an audio tar press (t) or an audio directory press (d)"
read option
case $option in
d)
cd "$source"
echo "please specify full path to directory you want to be... (6 Replies)
I have a requirement to perform specific set of tasks based on server , So I want to have the condition(s) defined based on server. Here is the script I came up with and I have read multiple blogs and couldn`t find any mistake from my script. Can you guide on what I am overlooking here ?
... (2 Replies)
Discussion started by: Varja
2 Replies
LEARN ABOUT SUSE
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)NAME
crontab - maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user] file
crontab [-u user] [-l | -r | -e]
DESCRIPTION
Crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have
their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the cron.allow file does not
exist but the cron.deny file does exist, then you must not be listed in the cron.deny file in order to use this command. If neither of
these files exists, only the super user will be allowed to use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines
"your" crontab, i.e., the crontab of the person executing the command. Note that su(8) can confuse crontab and that if you are running
inside of su(8) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is
given.
The -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
SEE ALSO crontab(5), cron(8)FILES
/etc/cron.allow
/etc/cron.deny
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 29 December 1993 CRONTAB(1)