10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Please tell me the script, if any user ping my pc so leave his ip, mac and other identity on my pc. (1 Reply)
Discussion started by: abhihot95
1 Replies
2. UNIX for Advanced & Expert Users
How can i track all the files accessed by script. The script is supposed to bring up my application and this script is just the main script which inturn calls another scripts and executable. I need to know all the the files this main script calls and the files accessed by all the other scripts... (2 Replies)
Discussion started by: chacko193
2 Replies
3. Shell Programming and Scripting
Hi, wondering if it's been asked before but didn't find matches from google. Basically I have this line:
myvar=$(echo -e "a\tb")
Now somehow the '\t' from the echo output gets replaced with white space and then stored in $myvar.
It creates a problem for me later to use tab as delimiter to do... (2 Replies)
Discussion started by: birddie
2 Replies
4. Shell Programming and Scripting
i have a scenario where i need a script that monitors a process "Monitor" based on process id... there can be any number of instances of this running... i start this across 4 servers in NFS. Now i need a file which has the process ids of the process that are currently in execution at any... (9 Replies)
Discussion started by: niteesh_!7
9 Replies
5. Shell Programming and Scripting
Hello,
Sorry for the poor tilte but I still don't know how to this.
Here is my problem.
I have to huge log file. In this log file I can know where is stored all my files. As I have to get a reporting of of files I only need to keep the file name but I don't know how to do it. I hope you... (5 Replies)
Discussion started by: Aswex
5 Replies
6. Shell Programming and Scripting
Hi Dudes,
Can you please suggest me how to create a logfile to track the below script output ? Thanks
#!/bin/ksh
# backup the "std" I/P file descriptor
exec 5<&0
#echo "Proceed ?"
while read config_line; do
# backup the I/P file descriptor of "while" block
exec 6<&0
# restore the... (2 Replies)
Discussion started by: shirdi
2 Replies
7. Shell Programming and Scripting
Hello,
I am trying to write a script that turns off the screensaver for a certain period of time, then come back on. I have had it up and running for a while, but then I decided to refactor it a bit for my family members that are less computer savvy.
I am starting a subshell for the "meat" of... (4 Replies)
Discussion started by: Narnie
4 Replies
8. Shell Programming and Scripting
I found some posts describing how to completely clean out a mailbox in Unix/Linux. But I want to keep the 50 most recent messages. Any ideas out there?
Thanks! (3 Replies)
Discussion started by: OPTIMUS_prime
3 Replies
9. UNIX for Dummies Questions & Answers
Like the topic says, does anyone know if it is possible to check to see when an FTP only user has logged in? Because the shell is /bin/false and they are only using FTP to access the system doing a "finger" or "last" it says they have never logged in.
Is there a way to see when ftp users log in... (1 Reply)
Discussion started by: LordJezo
1 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I am not aware whether any one has posted this early or not.
I am creating a house keeping script in which I give the user two options:
1. creating a zip file.
2. removing all files given by user.
Before taking any action I am asking user to
enter full path of file or files to be... (7 Replies)
Discussion started by: Rakesh Bhat
7 Replies
ns_sched(3aolserver) AOLserver Built-In Commands ns_sched(3aolserver)
__________________________________________________________________________________________________________________________________________________
NAME
ns_after, ns_cancel, ns_pause, ns_resume, ns_schedule_daily, ns_schedule_proc, ns_schedule_weekly, ns_unschedule_proc - commands
SYNOPSIS
ns_after seconds {script | procname ?args?}
ns_cancel id
ns_pause id
ns_resume id
ns_schedule_daily ?-thread? ?-once? hour minute {script | procname ?args?}
ns_schedule_proc ?-thread? ?-once? interval {script | procname ?args?}
ns_schedule_weekly ?-thread? ?-once? day hour minute {script | procname ?args?}
ns_unschedule_proc id
_________________________________________________________________
DESCRIPTION
ns_after
run the specified script or procedure after the specified number of seconds
ns_after returns an id which can be used with the ns_pause, ns_cancel and ns_resume apis.
ns_cancel
stops the scheduled running of the id returned by an ns_after
returns 1 if unscheduled 0 if the script of procedure couldn't be unscheduled
ns_pause
pauses the scheduled running of the id returned by an ns_after
returns 1 if paused, 0 if the script of procedure couldn't be paused
ns_resume
resumes the scheduled running of the id returned by an ns_after
returns 1 if resumed, 0 if the script of procedure couldn't be resumed
ns_schedule_daily
ns_schedule_daily runs the specified Tcl script or procedure (procname) once a day at the time specified by hour and minute. The
hour can be from 0 to 23, and the minute can be from 0 to 59.
Specify -thread if you want a thread created to run the procedure. This will allow the scheduler to continue with other scheduled
procedures. Specifying -thread is appropriate in situations where the script will not return immediately, such as when the script
performs network activity.
Specify -once if you want the script to run only one time. The default is that the script will be re-scheduled after each time it is
run.
ns_schedule_daily returns an id number for the scheduled procedure that is needed to stop the scheduled procedure with ns_unsched-
ule_proc.
ns_schedule_proc
ns_schedule_proc runs the specified Tcl script or procedure (procname) at an interval specified by interval. The interval is the
number of seconds between runs of the script.
Specify -thread if you want a thread created to run the procedure. This will allow the scheduler to continue with other scheduled
procedures. Specifying -thread is appropriate in situations where the script will not return immediately, such as when the script
performs network activity.
Specify -once if you want the script to run only one time. The default is that the script will be re-scheduled after each time it is
run.
ns_schedule_proc returns an id number for the scheduled procedure that is needed to stop the scheduled procedure with ns_unsched-
ule_proc.
ns_schedule_weekly
ns_schedule_weekly runs the specified Tcl script or procedure (procname) once a week on the day specified by day and the time speci-
fied by hour and minute. The day can be from 0 to 6, where 0 represents Sunday. The hour can be from 0 to 23, and the minute can be
from 0 to 59.
Specify -thread if you want a thread created to run the procedure. This will allow the scheduler to continue with other scheduled
procedures. Specifying -thread is appropriate in situations where the script will not return immediately, such as when the script
performs network activity.
Specify -once if you want the script to run only one time. The default is that the script will be re-scheduled after each time it is
run.
ns_schedule_weekly returns an id number for the scheduled procedure that is needed to stop the scheduled procedure with ns_unsched-
ule_proc.
ns_unschedule_proc id
ns_unschedule_proc stops a scheduled procedure from executing anymore. The scheduled procedure to be stopped is identified by its
id, which was returned by the ns_schedule* function that was used to schedule the procedure.
EXAMPLES
ns_after ns_cancel ns_pause ns_resume
This example illustrates a web interface used to manage jobs. Depending on the action provided a job can be created, cancelled,
paused or resumed.
set action [ns_queryget action] set job [ns_queryget job] switch $action {
create {
set job [ns_after 10 [ns_queryget script]]
ns_puts "Job created with id: $job"
}
cancel {
if {[ns_cancel $job]} {
ns_puts "Job $job cancelled"
} else {
ns_puts "Job $job not cancelled"
}
}
pause {
if {[ns_pause $job]} {
ns_puts "Job $job paused"
} else {
ns_puts "Job $job not paused
}
}
resume {
if {[ns_resume $job]} {
ns_puts "Job $job resumed"
} else {
ns_puts "Job $job couldn't be resumed"
}
}
default {
ns_puts "Invalid action $action"
} }
ns_schedule_daily
This example defines a script called rolllog that uses ns_accesslog to roll the access log to a file with an extension containing
the current date. The ns_schedule_daily function is used to execute the rolllog script on a daily basis.
# Script to roll and rcp log file to host "grinder" proc rolllog {} {
set suffix [ns_strftime "%y-%m-%d"]
set new [ns_accesslog file].$suffix
ns_accesslog roll $new
exec rcp $new grinder:/logs/[file tail $new] } # Schedule "rolllog" to run at 3:30 am each morning ns_schedule_daily -thread 3
30 rolllog
ns_schedule_proc proc dosomething blah {
ns_log Notice "proc with arg '$blah'" } ns_schedule_proc 10 dosomething $arg1
SEE ALSO
KEYWORDS
schedule pause resume unschedule cancel after
AOLserver 4.0 ns_sched(3aolserver)