Phpmotion is an audio/video website software or template. It is based on apache, php, mysql, perl and some audio and video players and converters.

System Requirements :

• apache web server with mod_rewrite, mod_perl.
• php 4 or 5
• ffmpeg-php
• php-devel
• php-mysql
• ffmpeg
• ffmpeg-devel
• ffmpeg-php
• flvtool2
• mencoder
• mplayer
• fvec
• phpshield loader for php
• mysql-server
• mysql-devel.

PHP Settings:

• - open_basedir = (no value)
• - upload_max_filesize = 100M
• - post_max_size = 100M
• - max_execution_time = 1500
• - session.gc_maxlifetime = 14000
• - safe_mode = off
• - Thread saftery = disabled
• - enable_dl = On

Installation and configuration (CentOS 5):

Step 1: Install apache , mysql and php

#yum install httpd httpd-devel mod_perl php php-devel php-mysql mysql mysql-server mysql-devel

Step 2: Install rpmforge repo for CentOS

#rpm -ivh http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.1-1.el5.rf.i386.rpm
#rpm –import http://apt.sw.be/RPM-GPG-KEY.dag.txt
#yum install mplayer ffmpeg flvtool2 mencoder

Step 3: Install fvec

#mkdir fvec
#cd fcec
#wget http://www.sothinkmedia.com/download/fvec.tar.gz
#tar xvfz fvec.tar.gz
#tar xvfz fvec.tar.gz
#cd ..
#mv fvec /usr/bin/

Step 4: Install phpshield loaders

#mkdir phpshield
#wget http://phpshield.com/loaders/phpshield.loaders.linux.zip
#unzip phpshield.loaders.linux.zip
#cp phpshield.5.1.lin /usr/lib/php/modules/

(Replace phpshield.5.1.lin with your version of php).

#cd ..
#rm -rf phpshield

Add following line in /etc/php.ini
extension=phpshield.5.1.lin

Step 5: Install ffmpeg-php

#cd /usr/src
#wget http://garr.dl.sourceforge.net/sourceforge/ffmpeg-php/ffmpeg-php-0.6.0.tbz2
#tar -xjf ffmpeg-php-0.6.0.tbz2
#cd ffmpeg-php-0.6.0
#phpize
#./configure && make && make install

Step 6: Download and configure phpmotion

#cd /usr/src
#wget http://downloads.phpmotion.com/V3.5/php5/phpmotion.zip
#unzip phpmotion.zip -d /var/www/html/
#chown -R apache:apache /var/www/html/phpmotion
#chmod -R 755 /var/www/html/phpmotion
#cp -ai /var/www/html/phpmotion/cgi-bin/* /var/www/cgi-bin

Edit the file /var/www/cgi-bin/uu_default_config.pm and make following changes in respected lines.

temp_dir => $ENV{‘DOCUMENT_ROOT’} . ‘/phpmotion/temp/’,
upload_dir => $ENV{‘DOCUMENT_ROOT’} . ‘/phpmotion/uploads/avi/’,
redirect_url => ‘/phpmotion/uploader_finished.php’,
path_to_upload => ‘/phpmotion/uploads/avi/’,

Edit the file /var/www/cgi-bin/audio/uu_default_config.pm and make following change in respected lines.

temp_dir => $ENV{‘DOCUMENT_ROOT’} . ‘/phpmotion/temp/’,
upload_dir => $ENV{‘DOCUMENT_ROOT’} . ‘/phpmotion/uploads/audio/’,
redirect_url => ‘/phpmotion/audio_uploader_finished.php’,
path_to_upload => ‘/phpmotion/uploads/audio/’,

Edit the file /var/www/html/phpmotion/.htaccess and change “RewriteBase /” to
“RewriteBase /phpmotion”

Step 7: Configure mod_perl in apache

Edit the file /etc/httpd/conf.d/perl.conf

change Following

Alias /phpmotion /var/www/html/phpmotion

Leave everything else as it is.

change AllowOverride to all for directory “/var/www/html” in “/etc/httpd/conf/httpd.conf” file (This is insecure and dangerous for public servers).

Now start the apache server as

#/etc/init.d/httpd start

Step 8: Create mysql database and user.

Start the mysql server

#/etc/init.d/mysqld start

login to mysql

#mysql

You will see mysql command line as under

mysql>

Run the following query on the mysql command line.

mysql>create database ‘dbname’ ;
mysql>grant all on dbname.* to ‘dbuser’@'localhost’ identified by ‘dbpassword’ ;
mysql>flush privileges;

(change dbname,dbuser and dbpassword accoring to your choice).

Step 9:Install the phpmotion

Now open the browser and enter the url of your server in the address bar as under:

http://ipaddressofyourserver/phpmotion/setup

Follow the instructions. And delete of rename the /var/www/html/phpmotion/setup folder after installation.

Hopefully you should now get phpmotion running on your server.

If you get any error at any moment in the process please revert back in the same post.

Anoop

• 0 Comments

Roaming profiles are, perhaps, the bane of being a network administrator. They can potentially cause more problems than they solve, slow down the login process to a crawl, are difficult to diagnose and, generally speaking, are frowned upon by seasoned network administrators. Having said this, they’re a feature that is high in demand among both users and upper-management staff and are, therefore, here to stay.A roaming profile essentially allows users to have their documents, desktop layout and settings follow them as they log in from one computer to another. Roaming profiles are stored on a central server in a domain. When logging in, Windows copies the user’s profile from the server to the local computer. When the user logs off, Windows copies the changed user profile data back to the server for storage.
Unfortunately, this both solves and creates additional problems. As user profiles increase in size, they can begin to be as large as 20, 50, 100, 1,000 megabytes or even more. This increase in size causes delays in logging in, as it takes time for the user’s profile to be copied from the server to the local computer, and back again at logoff. Additionally, when the user logs in to multiple computers at the same time, the last computer to log out “wins” as far as what the default settings should be.
Sounds like fun, right? Let’s begin.
Adjust your configuration file on the Samba server to include the following:
[global]
domain logons = yes
domain master = Yes
logon drive = P:
logon home = \\%L\%U
logon path = \\%L\profile\%U
netbios name = fluffygerbil
os level = 255
preferred master = yes
security = user
wins support = yes
workgroup = fluffygroup

[profile]
path = /cifs/profile
read only = no
profile acls = yes
create mode = 0600
directory mode = 0700
browseable = no You’ll also need to make sure that the necessary directories exist with the appropriate permissions:
# mkdir -p /cifs/profile
# chmod 1755 /cifs/profile Simply restart the Samba server, and you should be good to go.
If you run into problems, you have one of two available options using the Group Policy (gpedit.msc) console on each Windows client:
1. Enable the Do not check for user ownership of Roaming Profile Folders setting and reboot. From the Windows description of this option: “For Windows 2000 Professional pre-SP4 and Windows XP pre-SP1 operating systems, the default file permissions for the newly generated profile are full control access for the user and no file access for the administrators group. No checks are made for the correct permissions if the profile folder already exists. For Windows Server 2003 family, Windows 2000 Professional SP4 and Windows XP SP1, the default behavior is to check the folder for the correct permissions if the profile folder already exists, and not copy files to or from the roaming folder if the permissions are not correct. By configuring this setting, you can alter this behavior. If you enable this setting Windows will not check the permissions for the folder in the case where the folder exists. If you disable or do not configure this setting AND the roaming profile folder exists AND the user or administrators group not the owner of the folder, Windows will NOT copy files to or from the roaming folder. The user will be shown an error message and an entry will be written to the event log. The user’s cached profile will be used, or a temporary profile issued if no cached profile exists. Note: The setting must be configured on the client computer not the server for it to have any effect because the client computer sets the file share permissions for the roaming profile at creation time. Note: The behavior when this setting is enabled is exactly the same behavior as in Windows 2000 Professional pre-SP4 and Windows XP Professional.”
- or -
2. Enable the Only allow local user profiles setting (thus forgetting completely about roaming user profiles) and reboot. From the Windows description of this option: “This setting determines if roaming user profiles are available on a particular computer. By default, when roaming profile users log on to a computer, their roaming profile is copied down to the local computer. If they have already logged on to this computer in the past, the roaming profile is merged with the local profile. Similarly, when the user logs off this computer, the local copy of their profile, including any changes they have made, is merged with the server copy of their profile. Using the setting, you can prevent users configured to use roaming profiles from receiving their profile on a specific computer. If you enable this setting, the following occurs on the affected computer: At first logon, the user receives a new local profile, rather than the roaming profile. At logoff, changes are saved to the local profile. All subsequent logons use the local profile. If you disable this setting or do not configure it, the default behavior occurs, as indicated above. If you enable both the “Prevent Roaming Profile changes from propagating to the server” setting and the “Only allow local user profiles” setting, roaming profiles are disabled. Note: This setting only affects roaming profile users.”
Again, seasoned network administrators tend to favor option #2.
For comparison, here’s what an actual Windows Server will require for you to set up roaming profiles.
Note: Windows clients will expect the following permissions to exist for all roaming profile, regardless of whether a Windows or Samba server (thus our attempt to mimick with the chmod permission command).
Table 1: NTFS Permissions for Roaming Profile Parent Folder Windows User Account Minimum permissions required Creater/Owner Full Control, Subfolders And Files Only Administrator None Security group of users needing to put data on share List Folder/Read Data, Create Folders/Append Data – This Folder Only Everyone No Permissions Local System Full Control, This Folder, Subfolders And Files Table 2: Share Level (SMB) Permissions for Roaming Profile Share Windows User Account Default Permissions Minimum permissions required Everyone Full Control No Permissions Security group of users needing to put data on share N/A Full Control Table 3: NTFS Permissions for Each Users Roaming Profile Folder Windows User Account Default Permissions Minimum permissions required %Username% Full Control, Owner Of Folder Full Control, Owner Of Folder Local System Full Control Full Control Administrators No Permissions No Permissions Everyone No Permissions No Permissions

• 1 Comment

Summary:

SELinux is preventing the ftp daemon from reading users home directories
(./sysadmin).

Detailed Description:

SELinux has denied the ftp daemon access to users home directories (./sysadmin).
Someone is attempting to login via your ftp daemon to a user account. If you
only setup ftp to allow anonymous ftp, this could signal a intrusion attempt.

Allowing Access:

If you want ftp to allow users access to their home directories you need to turn
on the ftp_home_dir boolean: “setsebool -P ftp_home_dir=1″

Fix Command:

setsebool -P ftp_home_dir=1

Additional Information:

Source Context unconfined_u:system_r:ftpd_t:s0
Target Context system_ubject_r:user_home_dir_t:s0
Target Objects ./sysadmin [ dir ]
Source vsftpd
Source Path /usr/sbin/vsftpd
Port
Host client.0.168.192.in-addr.arpa
Source RPM Packages vsftpd-2.0.7-1.fc10
Target RPM Packages
Policy RPM selinux-policy-3.5.13-18.fc10
Selinux Enabled True
Policy Type targeted
MLS Enabled True
Enforcing Mode Enforcing
Plugin Name ftp_home_dir
Host Name localhost.localdomain
Platform Linux localhost.localdomain 2.6.27.5-117.fc10.i686
#1 SMP Tue Nov 18 12:19:59 EST 2008 i686 athlon
Alert Count 2
First Seen Thu 11 Jun 2009 10:39:11 PM IST
Last Seen Thu 11 Jun 2009 10:39:11 PM IST
Local ID 58df28b6-8505-406d-9ae1-1099d9a182ab
Line Numbers

Raw Audit Messages

node=client.0.168.192.in-addr.arpa type=AVC msg=audit(1244740151.879:265): avc: denied { read } for pid=5402 comm=”vsftpd” name=”sysadmin” dev=dm-0 ino=3784776 scontext=unconfined_u:system_r:ftpd_t:s0 tcontext=system_ubject_r:user_home_dir_t:s0 tclass=dir

node=client.0.168.192.in-addr.arpa type=SYSCALL msg=audit(1244740151.879:265): arch=40000003 syscall=5 success=no exit=-13 a0=b90c3030 a1=98800 a2=b7f91000 a3=bfbc72d8 items=0 ppid=5397 pid=5402 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm=”vsftpd” exe=”/usr/sbin/vsftpd” subj=unconfined_u:system_r:ftpd_t:s0 key=(null)

• 0 Comments

Hi

Following is the step-by-step how to install and configure DNS server in Linux.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>
Step1: Ensure that yum is installed and working properly in your system.

Step2: Install bind , bind-chroot and caching-nameserver with the help of yum.

$yum install -y bind bind-chroot caching-nameserver

Step3: Create the main configuration file for the DNS server as following-:

$cp /etc/named.caching-nameserver.conf /etc/named.conf

Step4: Now edit the following enteries in the /etc/named.conf file

Quote:

options {
listen-on port 53 { any; };
listen-on-v6 port 53 { ::1; };
directory “/var/named”;
dump-file “/var/named/data/cache_dump.db”;
statistics-file “/var/named/data/named_stats.txt”;
memstatistics-file “/var/named/data/named_mem_stats.txt”;
allow-query { any; };
recursion yes;
forwarders {
yourdnsserver1;
yourdnsserver2;
};
};

logging {
channel default_debug {
file “data/named.run”;
severity dynamic;
};
};

zone “.” IN {
type hint;
file “named.ca”;
};

zone “yourdomain.com” IN {
type master;
file “yourdomain.com.zone”;
allow-update { none; };
};

Step5: Now create the file yourdomain.com.zone in /var/named/chroot/var/named/

$vi /var/named/chroot/var/named/yourdomain.com.zone

and copy following code in that file(don’t forget to replace yourdomain.com with your actual domain name.

Quote:

$TTL 86400
@ IN SOA yourdomain.com root.yourdomain.com (
42 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum

IN NS yourdomain.com
IN A ipaddress.of.the.server
IN AAAA ::1

if you want ,you can add new hosts , nameservers or mail servers in this file.

Step6: disable selinux if you are not familiar with it. and run following commands

$chkconfig named on
$service named start

if everything goes well then you have done.

you can trouble shoot your server by following commands.

$bind-chroot-admin -d
$bind-chroot-admin -e

Step7:now change your system’s dns server from /etc/resolve.conf file

$vi /etc/resolve.con

nameserver ipaddress.of.the.server

:wq

Step8:Now its time to check your dns server .

$dig yourdomain.com

To check the server for Internet

$dig google.com

This is simple how to. For detail revert back.

Cheers

• 2 Comments

LAMP is short for Linux, Apache, MySQL, PHP. This tutorial shows how you can install an Apache2 webserver on a CentOS 5.3 server with PHP5 support (mod_php) and MySQL support.

Step 1
Suppose we have as system with hostname server1.example.com and the IP address 192.168.0.100. These settings might differ for you, so you have to replace them where appropriate.

Step 2 Installing MySQL 5.0
To install MySQL, we do this:

$yum install mysql mysql-server

Then we create the system startup links for MySQL (so that MySQL starts automatically whenever the system boots) and start the MySQL server:

$chkconfig –levels 235 mysqld on
$/etc/init.d/mysqld start

Run

$mysqladmin -u root password yourrootsqlpassword
$mysqladmin -h server1.example.com -u root password yourrootsqlpassword

to set a password for the user root (otherwise anybody can access your MySQL database!).

Step 3 Installing Apache2
Apache2 is available as a CentOS package, therefore we can install it like this:

$yum install httpd

Now configure your system to start Apache at boot time…

$chkconfig –levels 235 httpd on

… and start Apache:

$/etc/init.d/httpd start

Now direct your browser to http://192.168.0.100, and you should see the Apache2 placeholder page:
Apache’s default document root is /var/www/html on CentOS, and the configuration file is /etc/httpd/conf/httpd.conf. Additional configurations are stored in the /etc/httpd/conf.d/ directory.

Step 4 Installing PHP5
We can install PHP5 and the Apache PHP5 module as follows:

$yum install php

We must restart Apache afterwards:

$/etc/init.d/httpd start

Step 5 Testing PHP5 / Getting Details About Your PHP5 Installation
The document root of the default web site is /var/www/html. We will now create a small PHP file (info.php) in that directory and call it in a browser. The file will display lots of useful details about our PHP installation, such as the installed PHP version.

$vi /var/www/html/info.php
< ?php
phpinfo();
?>

Now we call that file in a browser (e.g. http://192.168.0.100/info.php):
As you see, PHP5 is working, and it’s working through the Apache 2.0 Handler, as shown in the Server API line. If you scroll further down, you will see all modules that are already enabled in PHP5. MySQL is not listed there which means we don’t have MySQL support in PHP5 yet.

Step 6 Getting MySQL Support In PHP5
To get MySQL support in PHP, we can install the php-mysql package. It’s a good idea to install some other PHP5 modules as well as you might need them for your applications. You can search for available PHP5 modules like this:

$yum search php

Pick the ones you need and install them like this:
yum install php-mysql php-gd php-imap php-ldap php-odbc php-pear php-xml php-xmlrpc
Now restart Apache2:

$/etc/init.d/httpd restart

Now reload http://192.168.0.100/info.php in your browser and scroll down to the modules section again. You should now find lots of new modules there, including the MySQL module:
Step 7 phpMyAdmin
phpMyAdmin is a web interface through which you can manage your MySQL databases.
First we enable the RPMforge repository on our CentOS system as phpMyAdmin is not available in the official CentOS 5.3 repositories:
On x86_64 systems:

$wget http://packages.sw.be/rpmforge-relea….rf.x86_64.rpm
$rpm -Uvh rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm

On i386 systems:

$wget http://packages.sw.be/rpmforge-relea…l5.rf.i386.rpm
$rpm -Uvh rpmforge-release-0.3.6-1.el5.rf.i386.rpm

phpMyAdmin can now be installed as follows:

$yum install phpmyadmin

Now we configure phpMyAdmin. We change the Apache configuration so that phpMyAdmin allows connections not just from localhost (by commenting out the stanza):

$vi /etc/httpd/conf.d/phpmyadmin.conf
#
# Web application to manage MySQL
#

#

# Order Deny,Allow
# Deny from all
# Allow from 127.0.0.1
#

Alias /phpmyadmin /usr/share/phpmyadmin
Alias /phpMyAdmin /usr/share/phpmyadmin
Alias /mysqladmin /usr/share/phpmyadmin

Next we change the authentication in phpMyAdmin from cookie to http:

$vi /usr/share/phpmyadmin/config.inc.php
[...]
/* Authentication type */
$cfg['Servers'][$i]['auth_type'] = ‘http’;
[...]

Afterwards, you can access phpMyAdmin under http://192.168.0.100/phpmyadmin/:

Enjoy

• 0 Comments