Comments for CodeWord: Apokalyptik

Comment on colorizing php cli scripts by Amos Batto

Amos Batto — Fri, 25 Jan 2013 23:59:19 +0000

What I do is include this file:
//file: terminalcolores.php
//Bash Terminal Color Codes:
$BLACK = "33[30m";
$RED = "33[31m";
$GREEN = "33[32m";
$BROWN = "33[33m";
$BLUE = "33[34m";
$PURPLE = "33[35m";
$CYAN = "33[36m";
$LIGHTGREY = "33[37m";

$DARKGREY = "33[1;30m";
$LIGHTBLUE = "33[1;34m";
$LIGHTGREEN = "33[1;32m";
$LIGHTCYAN = "33[1;36m";
$LIGHTRED = "33[1;31m";
$LIGHTPURPLE = "33[1;35m";
$YELLOW = "33[1;33m";
$WHITE = "33[1;37m";

$BLACKBACKGROUND = "33[40";
$REDBACKGROUND = "33[41";
$GREENBACKGROUND = "33[42";
$YELLOWBACKGROUND = "33[43";
$BLUEBACKGROUND = "33[44";
$MAGENTABACKGROUND = "33[45";
$CYANBACKGROUND = "33[46";
$WHITEBACKGROUND = "33[47";

$COLOROFF = "33[0m";

then I use it like this:

require("terminalcolors.php");
echo "{$RED}this is some red text{$COLOROFF}";

Comment on As Close to A Real Daemon As Bash Scripts Get by Anthony Bouch

Anthony Bouch — Wed, 23 Jan 2013 04:02:06 +0000

Excellent – thanks.

The only change I made was

start)
if [ -f $MY_PIDFILE ]; then
echo "Daemon is already running."
exit 0
fi
…

In cases where we want to be sure that there is only one instance of the daemon running.

Comment on Bash Tip: Closing File Descriptors by none

none — Mon, 26 Nov 2012 13:59:45 +0000

You should be redirecting stdin, stdout, and stderr to /dev/null……. instead of just closing them.

Comment on Bash Tip: Closing File Descriptors by nobody

nobody — Sun, 14 Oct 2012 08:49:10 +0000

Should closing stdio be:

exec 0<&- # close stdin

instead?

Comment on Logging post data by apokalyptik

apokalyptik — Fri, 21 Sep 2012 16:37:55 +0000

Nope. That was just the blog/me messing up the text when it was entered. Urldecoding it is the proper thing to do (otherwise it wouldn't run.) Glad it helped.

Comment on Logging post data by Dave O'Meara

Dave O'Meara — Sat, 01 Sep 2012 13:10:11 +0000

Great script. Exactly what I needed after studying the log files to find dozens of attempted posts to pages in the Joomla core, but not being able to see what the bad guy was trying to post. We're not running mod_php so I wasn't able to use .htaccess. Instead I used the .user.ini file (user-level add-on for php.ini). Once I got all the files in place, it worked great.
I changed gmdate() to date() to get the log entries in my time zone. Also, for some reason the sample code was urlencoded. I changed it back to simple php

Comment on Sockets and PHP — Part II: Working with our connection by apokalyptik

apokalyptik — Fri, 15 Jun 2012 18:42:02 +0000

Wow to find this I had to go WAAAAAY back…
http://web.archive.org/web/20020802063303/http://…

I'll get this up on the site some time. I can't believe how long ago this all was. I'd probably be very embarrassed by the code if I went back and read any of it now

Cheers!
DK

Comment on Sockets and PHP — Part II: Working with our connection by apokalyptik

apokalyptik — Fri, 15 Jun 2012 18:16:56 +0000

Thanks. That page is, indeed, gone. I'll see if I can locate it. It's been gone for a long time — You're the first to notice

Comment on Debian, ProFTPD, FTPS, TLS, SSL, and SSL23_GET_SERVER_HELLO:unknown protocol by Jay

Jay — Fri, 15 Jun 2012 04:17:54 +0000

Excellent, Very useful !

Comment on Sockets and PHP — Part II: Working with our connection by Annuello

Annuello — Tue, 15 May 2012 05:52:02 +0000

This is a great walk-through for sockets, but I can't find the first half. Your post "Published Articles-n-Stuff" has a link to "Sockets and PHP – Part I: Moving data from one place to another" but the link ( http://blog.apokalyptik.com/?page_id=220 ) is broken.