![]() Right now, I am just watching to see when ipUpdate drops out again. Maybe someone with more knowledge than me will chime in. The daily is an easy one and I don't know if it is run right after a reboot or not. I am fixing to st down with a book or two and read up on cron. I am surprised that editing the rc? file, as mentioned early on doesn't get the job done. So, Linux doesn't have to be rebooted like windows does. I had been running a Samba file server on the same machine I'm running 8.04 on for over a year without touching it. Open (STDERR, '>/dev/null') or die "Can't write to /dev/null: $!" ĭefined(my $pid = fork) or die "Can't fork: $!" Īre you rebooting everyday? If not, why not just remember to start ipUpdate when you do. Open (STDOUT, '>/dev/null') or die "Can't write to /dev/null: $!" Open (STDIN, '/dev/null') or die "Can't read /dev/null: $!" # Daemonize the process and write pid to pidfile ![]() My ($type, $code, $message) = (LOGFILE, ">$logfile") ![]() Mark("ERROR", "-99", "Fail to get the proxy IP of your machine") Fail to grep the IP address from ".$myUrl) Mark("ERROR", "-100", "Return message format error. Mark("INFO", "100", "$myUrl says your IP address is: $1") Mark("ERROR", $response->code, $response->message) Mark("ERROR", "-99", "Return content format error") #record successful update of the ip address DAMMIT why did I upgrade?!!!! :(Ĭhdir($PROGRAMDIR) || die "Unable to go to dir $PROGRAMDIR" I don't know enough about Perl to decipher what that subroutine is trying to do, but my guess is something that is not compatible with 9.04. So, it seems to be erroring out in the daemonize() subroutine. I placed the "print" statements and it prints out 2.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |