Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 203
  • Last Modified:


I use Unix

Is there a command in perl where you can say something like:

In 30 min execute {
(stuff to execute)

And that it would do it, even if the user's browser is no longer open?  Thanks
1 Solution
  man at
  perldoc -f localtime

I've got to go now, but I'll post some code tomorrow (or someone else will do it before...).

Unless you had Perl spawn another process at runtime,
the only way you'd get it going is to system an "at" command.
A keepalive connection would (in theory) work but it's doubtful
they're going to keep a page open for 30 mins...

jknickelbeinAuthor Commented:
Using the at command is kinda what martinag already said.... if you can explain how to use it, I'll award to him the points.
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

jknickelbeinAuthor Commented:
Really, all I need done, is that 30 minutes after my user logs into my script, I want to delete a certain file, thus expiring the session.
# Random file name
$file = "exec" . time . "pid$$.ex"; # millisecs since 1970 and pid should be enough random

# Write file that should be "executed"
open (FILE, ">$file") or die "can't open $file for output: $!";
print FILE "rm ..."; # The command
close FILE;

# Calculate time
@time = localtime;
$h = $time[2];
$m = $time[1] + 30;
if ($m > 59) {
  $h = 0 if $h++ == 24;
  $m -= 60;

# Set timer
system("at -f $file " . sprintf("%2d:%2d", $h, $m));


Another approach you could use would be to simply keep a process excecuting on the server which makes sure everything is cleared out if it is 30 minutes old... just clearing the directory every 30 minutes would work, but then some people would have shorter "login" times than others.

Try something like this:
Build a perl script which will check the directory every minute for aged files and delete them.  When it launched, have the script record its PID (process id) to a file.

No, have your other perl scripts which users interact with have a function that just occasionally checks that data file for the pid and checks to see if it is still alive.  If it isnt, have it reexecute ... that is your safe guard...

And voila:)  Every thing will run fine...
i still think it would be simpler just to have you login script clear out old entries... it would not take much process time...
jknickelbeinAuthor Commented:
Ok... thanks guys!

Cov - as long as it should take to long (process time) to clear out all over 30min. entries, that's probably what I'll do.

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now