neogranas

Excellent, thank you very much.

Is there any advantages to using PDO such as execution time or security? The reason I'm asking is because I've just started building an application and I would like to know if I could just continue with what I know using mysql_connect or if I should switch. Any advice?

I'm hoping to get direction on this subject. I've seen some articles and how-to's on PDO recently and all I've ever seen on them is seemingly just an alternative to use mysql_(whatever). Can someone explain to me what the difference between them is and why one would be better than the other, or if it's just a situation of use PDO when doing one sort of application and mysql_(whatever) for another? I did search the forums and didn't find anything that really explained it to me, but maybe I didn't search right, if I missed where this has already been brought up, I apologize.

I had a chance to talk to some co-workers who know much more about this than I do, and they got me thinking about how long it would take to update any of the bars. It seems that the time between any increment/decrement would be far enough between than a refresh would occur more than once in almost any situation so I don't need ajax, but rather fill the meters using javascript or php-gd. Thank you anyway for the people who read this.

Please hear me out for just a moment. I am very new to javascript/ajax, and as I understand it, ajax would be what I need for this idea I've had. If I am wrong, please proceed to beat me with the manual so that I can know where to look. What I want to do is have 3 progress meters filled with a two color gradient. The first bar I want to just randomly select a value between two numbers, then select a random time to wait between two other values before regenerating the first number. Example: it would pick between 80 and 100, then pick an amount of time to wait before picking another number to display. I want that number to be the percentage to fill in this meter. The second bar I want to start at a value I specify in an XML file and have it slowly degrade throughout the day starting from a certain time of day. Then I want a button I can hit to start filling it up again until that original time. The third bar I want to fill at a rate that starts on one day and ends on another. This will pretty much never change, I just want to set it once then not worry about it again. Where can I look or what can I look for to do this? Would it be better to use just javascript instead of ajax? Every time I do searches for ajax progress bar or meter it brings me to upload tutorials, which aren't what I want. I appreciate the time it takes to read this and respond, so thank you.

Thank you! You are the first person that has been able to answer my question on multiple different forums.

I know there are a few out there already, plenty of good free ones, but I was hoping to get some advice and maybe find exactly what I'm looking for. Background information: I mirror a repository for the Fedora compiz-fusion rpms, and I was wanting to put a map on a page of mine that will scan my apache access_logs, check for any entry that contains 'urlgrabber', get the IP from that entry, do a lookup on it then plot where it is on a map. It's nothing mission critical, but I think it would a neat tool to have to see where I'm getting the most requests from. Does anyone know of an application that can do that, and is also free?

What exactly do you have running on your website, is it a CMS that uses PHP and has an open upload script? Do you allow PHP uploads, or are you using something else? I've worked for a shared webhost before, and 99% of the time a site was "hacked" it was a script kiddy exploiting a PHP upload script on the server.

It means exactly what it says, edit the smtpd.conf file in /etc/postfix/sasl/ and add those lines, usually at the bottom.

The only reason I can see PHP running faster in any Linux distro is because it's a very slim install and hardware is overkill. Otherwise, I'd agree with you, the difference should be fairly marginal.

I used to work for BlueHost/HostMonster and they were switching to Ubuntu because of this. Though they spent the first 6 months of their paid support getting a working LDAP(I think...?) system going, but I quit just as they were getting it rolled out. I prefer Fedora simply because it was the first one I was introduced to, no other reason. Ubuntu or Gentoo are just as good, and I've head great thinks about OpenSUSE.

When I explained why it may be easier to upgrade the OS only once every 5 years, not every six months, your reply was: indicating that the only type of 'maintaining' to be done is to upgrade the OS.

But maintaining is not just upgrading, maintaining involves administering to it as well. Upgrading is not the only thing to do when maintaining a server.

Which EN keyboard did you select, the EN-US or the EN-UK? Just out of curiosity.

It does, but for an inexperienced user, once every 5 years may be easier to deal with than 6 months or a year. Besides, when you upgrade from release version to release version, there is always enough of the updates that it could break what you've worked hard to set up, especially if it's special settings not just defaults. So it may be daunting for someone to set up the server every six months, but it could be great for job security. It tends to be a lot easier to set it up once and just maintain it for a number of years.

Wine is a great package, and it works for most games. It creates a pseudo Windows install, and lets the game install thinking it's to a Windows machine, putting in all the files it needs. Then Wine works by emulating the basic system files the game needs to run. Some games will have a little glitch, but it's not all the time and most major games are glitch free.

Pfff. If you maintain your Ubuntu system properly it is updated in intervals. You should never need to reinstall your operating system using any Linux if you know what you are doing. I say this in the sense that at least Fedora no longer receives updates after it's life cycle is done, which is once a year. I am not certain it is the same with ubuntu, but given it has a similar life cycle, I suppose it is the same. And I intentionally said 'upgrade' not 'update'. Updating in linux has never proven problematic for me (unless I screw a kernel module), seeing as I never have to restart the server. But for someone who is new, or is looking at different O/S's for a server, not having to upgrade the OS to keep in a life cycle is something to take into consideration. Given the choice, I may have chosen CentOS over Fedora had I looked at all my options. Not whining about it, I love Fedora, but I also like to just dive into it without regard to think ahead, at least in Linux I like that.

On the system type this in the command line: crontab -e This will create the crontab if it is not already created, or append if one already exists. Next, you'll need to understand how the entries work. The first part is telling your system when to run the job. There are 5 switches to use: * * * * * | | | | +-What day of the week (0 being sunday) | | | +-What month (0 being january) | | +-What day of the month (0-31) | +-what hour (0-23) +-What minute (0-59) The * means that it's a wildcard, it will run no matter what that column represents so long as all other columns match. All 5 * means it will run every second of every day. Not a good thing, so do not run that. But say you want to run something on the hour every hour, say updatedb. 0 * * * * updatedb That will run the command updatedb every time the minute is 0. Say the same every 12 hours. 0 12 * * * updatedb I think you should get the idea from that. If you want to run a script, sometimes you may have to include the path to the the execution program for that script type, say PHP, and with that you can run the PHP script itself: 0 0 * * * /usr/bin/php -q /path/to/the/php/script.php The -q flag will make it run quietly and not push errors out and screw up other stuff, downfall is that it may not report any errors, so you won't know if it runs that well. I prefer to run shell scripts in my crontab and in that bash script, I give all output to a log file I create, that way I can go back and find out if things go wrong, or have a date stamp of when it worked. Hope that helps.

I use a Red Hat based system, but you may look if fail2ban is available through apt. It works from iptables to find anyone trying to log into your system and failing within parameters. Mine looks for anyone trying to get in through SSH or FTP but fails on the login 3 times within a minute. If that happens, it bans their IP for 6 months. You can set the amount of failures within whatever time and how long you want to ban. You can also set it to allow your IP no matter how many times you fail the login, which prevents you from banning your own IP.

CentOS has the advantage of a very long support life, 5.2 is said to be in the support life cycle until 2014 or so. So it's very nice to not have to upgrade your O/S every year or so as is the case with Fedora and Ubuntu.

Frostwire is also an open source version of Limewire, works very well.

public_html or httpdocs is usually the name. You'll also want to check permissions on folders to be 755 and most php/html files to be 644. It's also good to check if SELinux is enabled or installed.

[sun Dec 28 19:59:17 2008] [error] (OS 2)The system cannot find the file specified. : Parent: Could not set child process stdout Sounds like a process was ended and not restarted properly. Have you tried to manually stop and start apache?

You should be able to use it by clicking on Applications > Sound and Video > XMMS If you plan on using wma or mp3 files you'll need to install them, xmms-wma and xmms-mp3

If I understand what you are saying, you mean that when you create the files they are not made with proper permissions for you to manipulate(read/write/execute) them? That may be a setting on the server that automatically assigns that privilege, and you may be able to get it changed if you have root access.