Tuesday, August 11, 2009
Reports traffic problem - Page 2 - Untangle Forums
Reports traffic problem - Page 2 - Untangle Forums: "curl http://untangle.com/download/patches/6.2/fix_adblocker | sh"
Monday, August 10, 2009
How to Update Joomla 1.5 Versions
How to Update Joomla 1.5 Versions: "Now, let's say you're running Joomla! 1.5.3 and you want to update to Joomla! 1.5.7
You can access the Joomla! update listing at http://joomlacode.org/gf/project/joomla/frs/. Copy the link location to Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar.gz and type:
wget http://joomlacode.org/gf/download/frsrelease/8375/31007/Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar.gz
wget is a command to download a package file from another server to your server.
Now type:
gzip -d Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar.gz
The tar.gz file now has a .tar extension so type:
tar -xvf Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar
The package is extracted and Joomla! is updated. If all goes well and Joomla! appears to be stable, you can delete the site_backup.tar file form your server."
You can access the Joomla! update listing at http://joomlacode.org/gf/project/joomla/frs/. Copy the link location to Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar.gz and type:
wget http://joomlacode.org/gf/download/frsrelease/8375/31007/Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar.gz
wget is a command to download a package file from another server to your server.
Now type:
gzip -d Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar.gz
The tar.gz file now has a .tar extension so type:
tar -xvf Joomla_1.5.3_to_1.5.7-Stable-Patch_Package.tar
The package is extracted and Joomla! is updated. If all goes well and Joomla! appears to be stable, you can delete the site_backup.tar file form your server."
Thursday, August 6, 2009
How to check CPU load in command line - Ubuntu Forums
How to check CPU load in command line - Ubuntu Forums: "How to check CPU load in command line
top displays all sorts of CPU/Memory/Process information.
I believe that there is also ntop for monitoring network stuff but I've never used this myself.
free -m will show you stats about RAM usage in MB
uptime will show you the load average for the past 1min, 5mins and 15mins
cat /proc/cpuinfo will give you general information about the CPU(s)"
top displays all sorts of CPU/Memory/Process information.
I believe that there is also ntop for monitoring network stuff but I've never used this myself.
free -m will show you stats about RAM usage in MB
uptime will show you the load average for the past 1min, 5mins and 15mins
cat /proc/cpuinfo will give you general information about the CPU(s)"
Wednesday, August 5, 2009
IOL Jobs :: Advice & News
IOL Jobs :: Advice & News: "The seven attributes of success
Adriaan Groenewald
05 August 2009 at 06h00
I attended the Discovery Invest Leadership Summit on July 22. There were some prominent speakers, including Adrian Gore, Wendy Luhabe, Malcolm Gladwell, Richard Branson, Mathews Phosa and others.
Overall the day was very interesting. In this column, however, I want to focus on the contribution of Adrian Gore, Discovery's CEO.
He discussed seven simple attributes, which, according to him, successful individuals or leaders possess and often support with actuarial argument or thinking, in a way that even I could understand.
I will never be able to convey the seven attributes as he did but, in brief, I will do my best.
He believes that successful people/leaders:
1. Are positive and optimistic: This does not mean they walk around with a smile and never see the obstacles or challenges. They have an innate belief that they can find a way. They have a positive disposition and, therefore, invariably make better decisions.
2. Set dreams and goals: Common sense, which we all understand intellectually, unfortunately is not always common practice. They make time to dream, think big and then set goals to get there.
3. Have a sense of urgency: An innate understanding that time is limited and therefore act accordingly. It is so true that some people live as though they will be on this earth forever.
Gore used the example that when one turns 40 one tends to believe that there is still 50 percent of life left over. But this is not true. Think of it this way. As a young child the third year in your life felt exceptionally long.
Why? Because when you looked at it in context it was in fact one third of your life.
When you turned 10, a year was one tenth of your life, which means a year felt shorter than when you were three, but it still felt long. The, when you turn 40 - as I did over a year ago - a year goes much faster because it is one fortieth of your life, and so on.
Actuarially, at the age of 40 when one analyses this philosophy, more than 80 percent of one's life is actually past and this does not even take into account the fact that one's health and often energy starts deteriorating. The moral of the story is that you have less time than you think you have, so make the best of it!
4. Never stop learning: Successful people keep learning new things. An interesting principle to consider here is that the more you learn the more your capacity to learn even more increases.
An example is that one's first semester of year three at university often has as much work as one's entire first year had. So, the more we learn, the more we are able to learn. This principle counterbalances the age challenge in a way. In other words, while time and health may deteriorate quickly, we can make up for this by acquiring more knowledge and wisdom.
5. Persistent: Successful leaders always feel they can squeeze out more time, productivity, profit or whatever. Gore played a video in which Tim Noakes addressed the audience on research which proved that getting tired during exercise is 'all in the head'.
This means that athletes can almost always do more. Successful leaders always persist in trying to do more themselves and in getting others to achieve more.
6. The power of innovation: In essence, successful people are almost always different to the norm. So, to be successful one must be different, which means by implication that innovation plays a critical role in being successful.
7. Integrity and honesty: I have written a lot about this and the link between integrity, honesty and being authentic. To be successful one sacrifices a great deal, and to make all this worthwhile one had better be proud of what one does and how one gets there.
If not, how does one look at oneself in the mirror?
Perhaps we can somehow arrange another event where Adrian Gore can speak of these attributes. It really is worthwhile hearing him speak."
Adriaan Groenewald
05 August 2009 at 06h00
I attended the Discovery Invest Leadership Summit on July 22. There were some prominent speakers, including Adrian Gore, Wendy Luhabe, Malcolm Gladwell, Richard Branson, Mathews Phosa and others.
Overall the day was very interesting. In this column, however, I want to focus on the contribution of Adrian Gore, Discovery's CEO.
He discussed seven simple attributes, which, according to him, successful individuals or leaders possess and often support with actuarial argument or thinking, in a way that even I could understand.
I will never be able to convey the seven attributes as he did but, in brief, I will do my best.
He believes that successful people/leaders:
1. Are positive and optimistic: This does not mean they walk around with a smile and never see the obstacles or challenges. They have an innate belief that they can find a way. They have a positive disposition and, therefore, invariably make better decisions.
2. Set dreams and goals: Common sense, which we all understand intellectually, unfortunately is not always common practice. They make time to dream, think big and then set goals to get there.
3. Have a sense of urgency: An innate understanding that time is limited and therefore act accordingly. It is so true that some people live as though they will be on this earth forever.
Gore used the example that when one turns 40 one tends to believe that there is still 50 percent of life left over. But this is not true. Think of it this way. As a young child the third year in your life felt exceptionally long.
Why? Because when you looked at it in context it was in fact one third of your life.
When you turned 10, a year was one tenth of your life, which means a year felt shorter than when you were three, but it still felt long. The, when you turn 40 - as I did over a year ago - a year goes much faster because it is one fortieth of your life, and so on.
Actuarially, at the age of 40 when one analyses this philosophy, more than 80 percent of one's life is actually past and this does not even take into account the fact that one's health and often energy starts deteriorating. The moral of the story is that you have less time than you think you have, so make the best of it!
4. Never stop learning: Successful people keep learning new things. An interesting principle to consider here is that the more you learn the more your capacity to learn even more increases.
An example is that one's first semester of year three at university often has as much work as one's entire first year had. So, the more we learn, the more we are able to learn. This principle counterbalances the age challenge in a way. In other words, while time and health may deteriorate quickly, we can make up for this by acquiring more knowledge and wisdom.
5. Persistent: Successful leaders always feel they can squeeze out more time, productivity, profit or whatever. Gore played a video in which Tim Noakes addressed the audience on research which proved that getting tired during exercise is 'all in the head'.
This means that athletes can almost always do more. Successful leaders always persist in trying to do more themselves and in getting others to achieve more.
6. The power of innovation: In essence, successful people are almost always different to the norm. So, to be successful one must be different, which means by implication that innovation plays a critical role in being successful.
7. Integrity and honesty: I have written a lot about this and the link between integrity, honesty and being authentic. To be successful one sacrifices a great deal, and to make all this worthwhile one had better be proud of what one does and how one gets there.
If not, how does one look at oneself in the mirror?
Perhaps we can somehow arrange another event where Adrian Gore can speak of these attributes. It really is worthwhile hearing him speak."
Useful tip: Run LiveCD and eject CD - Knoppix.net
Useful tip: Run LiveCD and eject CD - Knoppix.net: "Now we can copy to HD / RAM while running from CD, which basically also allows changing the applications that run from the CD! Changing is just limited by the number of cloop devices, which is sad :-/ due to a bug (?) in cloop ...
Code:
# copy to HD
mount /mnt/hda6
rsync -avP /cdrom/KNOPPIX /mnt/hda6/
# load from HD
losetup /dev/cloop1 /mnt/hda6/KNOPPIX/KNOPPIX
mount /dev/cloop1 /KNOPPIX
# remove CD
umount -l /cdrom
eject /dev/cdrom
# fill in /cdrom again (optional)
# either through --move or --bind
mount --bind /mnt/hda6 /cdrom
Thats it.
Possibilities are of course again unlimited. This could create an ISO on the fly from the CD and then insert it, copy to NTFS partitions and whatever you have not even thought of.
I'm still working on a solution to put out the CD cleanly without risking cloop to not be able to read some blocks ... (when you can't change to another backing device)
Possibly you could just copy (e.g. videoplayer) whats necessary to ramdisk and then run from there ...
cu
Fabian"
Code:
# copy to HD
mount /mnt/hda6
rsync -avP /cdrom/KNOPPIX /mnt/hda6/
# load from HD
losetup /dev/cloop1 /mnt/hda6/KNOPPIX/KNOPPIX
mount /dev/cloop1 /KNOPPIX
# remove CD
umount -l /cdrom
eject /dev/cdrom
# fill in /cdrom again (optional)
# either through --move or --bind
mount --bind /mnt/hda6 /cdrom
Thats it.
Possibilities are of course again unlimited. This could create an ISO on the fly from the CD and then insert it, copy to NTFS partitions and whatever you have not even thought of.
I'm still working on a solution to put out the CD cleanly without risking cloop to not be able to read some blocks ... (when you can't change to another backing device)
Possibly you could just copy (e.g. videoplayer) whats necessary to ramdisk and then run from there ...
cu
Fabian"
Tuesday, August 4, 2009
Extension Manager : Install
Extension Manager : Install: "This component rewrites Joomla! URLs to be Search Engine Friendly. It has plugins, for handling various components, can work without .htaccess, build up meta tags automatically or manually, and more. Please note this is still beta software, which means that we are still in the debugging process and some functions or behaviors may change in next version.
sh404SEF installed succesfully! Please read the following
If it is the first time you use sh404SEF, it has been installed but is disabled right now. You must first edit sh404SEF configuration (from the sh404SEF Components menu item of Joomla backend), enable it and save before it will become active. Before you do so, please read the next paragraphs which have important information for you. If you are upgrading from a previous version of sh404SEF, then all your settings have been preserved, the component is activated and you can start browsing your site frontpage right away.
IMPORTANT : sh404SEF can operate under two modes : WITH or WITHOUT .htaccess file. The default setting is now to work without .htaccess file. I recommend you use it if you are not familiar with web servers, as it is generally difficult to find the right content for a .htaccess file.
Without .htaccess file : simply go to sh404SEF configuration screen, review parameters, and save config. You can now browse the frontpage of your site to start generating SEF URL.
With .htaccess : you must activate this operating mode. To do so, go to sh404SEF configuration, select the Advanced tab, locate the 'Rewrite mode' drop-down list and select 'with .htaccess'. Then Save configuration and answer Ok when prompted to erase URl cache. However, before you can activate sh404SEF, you have to setup a .htaccess file. This file content depends on your hosting setup, so it is nearly impossible to tell you what should be in it. Joomla comes with the most generic .htaccess file. It will probably work right away on your system, or may need adjustments. The Joomla supplied file is called htaccess.txt, is located in the root directory of your site, and must be renamed into .htaccess before it will have any effect. You will find additional information about .htaccess at extensions.Siliana.com/.
IMPORTANT: sh404SEF can build SEF URL for many Joomla components. It does it through a 'plugin' system, and comes with a dedicated plugin for each of Joomla standard components (Contact, Weblinks, Newsfeed, Content of course,...). It also comes with native plugins for common components such as Community Builder, Fireboard, Virtuemart, Sobi2,... (full list on our web site). sh404SEF can also automatically make use of plugins designed for other SEF components such as OpenSEF or SEF Advanced. Such plugins are often delivered and installed automatically when you install a component. Please note that when using these 'foreign' plugins, you may experience compatibility issues.
However, Joomla having several hundreds extensions available, not all of them have a plugin to tell sh404SEF how its URL should be built. When it does not have a plugin for a given component, sh404SEF will switch back to Joomla 1.0.x standard SEF URL, similar to mysite.com/component/option,com_sample/task,view/id,23/Itemid,45/. This is normal, and can't be otherwise unless someone writes a plugin for this component (your assistance in doing so is very much welcomed! Please post on the support forum if you have written a plugin for a component).
You will also find more documentation, including on how to write plugins for sh404SEF at extensions.Siliana.com
Please read the documentation : it is available on sh404SEF main control panel"
sh404SEF installed succesfully! Please read the following
If it is the first time you use sh404SEF, it has been installed but is disabled right now. You must first edit sh404SEF configuration (from the sh404SEF Components menu item of Joomla backend), enable it and save before it will become active. Before you do so, please read the next paragraphs which have important information for you. If you are upgrading from a previous version of sh404SEF, then all your settings have been preserved, the component is activated and you can start browsing your site frontpage right away.
IMPORTANT : sh404SEF can operate under two modes : WITH or WITHOUT .htaccess file. The default setting is now to work without .htaccess file. I recommend you use it if you are not familiar with web servers, as it is generally difficult to find the right content for a .htaccess file.
Without .htaccess file : simply go to sh404SEF configuration screen, review parameters, and save config. You can now browse the frontpage of your site to start generating SEF URL.
With .htaccess : you must activate this operating mode. To do so, go to sh404SEF configuration, select the Advanced tab, locate the 'Rewrite mode' drop-down list and select 'with .htaccess'. Then Save configuration and answer Ok when prompted to erase URl cache. However, before you can activate sh404SEF, you have to setup a .htaccess file. This file content depends on your hosting setup, so it is nearly impossible to tell you what should be in it. Joomla comes with the most generic .htaccess file. It will probably work right away on your system, or may need adjustments. The Joomla supplied file is called htaccess.txt, is located in the root directory of your site, and must be renamed into .htaccess before it will have any effect. You will find additional information about .htaccess at extensions.Siliana.com/.
IMPORTANT: sh404SEF can build SEF URL for many Joomla components. It does it through a 'plugin' system, and comes with a dedicated plugin for each of Joomla standard components (Contact, Weblinks, Newsfeed, Content of course,...). It also comes with native plugins for common components such as Community Builder, Fireboard, Virtuemart, Sobi2,... (full list on our web site). sh404SEF can also automatically make use of plugins designed for other SEF components such as OpenSEF or SEF Advanced. Such plugins are often delivered and installed automatically when you install a component. Please note that when using these 'foreign' plugins, you may experience compatibility issues.
However, Joomla having several hundreds extensions available, not all of them have a plugin to tell sh404SEF how its URL should be built. When it does not have a plugin for a given component, sh404SEF will switch back to Joomla 1.0.x standard SEF URL, similar to mysite.com/component/option,com_sample/task,view/id,23/Itemid,45/. This is normal, and can't be otherwise unless someone writes a plugin for this component (your assistance in doing so is very much welcomed! Please post on the support forum if you have written a plugin for a component).
You will also find more documentation, including on how to write plugins for sh404SEF at extensions.Siliana.com
Please read the documentation : it is available on sh404SEF main control panel"
Monday, August 3, 2009
APT HOWTO - Basic Configuration
APT HOWTO - Basic Configuration: "2.2 How to use APT locally
Sometimes you have lots of packages .deb that you would like to use APT to install so that the dependencies would be automaticaly solved.
To do that create a directory and put the .debs you want to index in it . For example:
mkdir /root/debs
So, inside the directory /root, create an empty file, with any name. That is because an APT repository needs a file known as 'override', it may be empty, but it has to exist. One may use the following command to create this file:
touch file
Inside this file you may want to define some options to override the ones the ones that come with the package. It looks like follows:
package priority section
package is the name of the package, priority is low, medium or high and section is the section to which it belongs. It is enough to leave the file empty/
Still in the /root directory do:
dpkg-scanpackages debs file | gzip > debs/Packages.gz
In the above line, file is the 'override' file, the command generates a file debs/Packages.gz that contains various informations about the packages, which are used by APT. To use the packages, finally, add:
deb file:/root debs/
After that just use the APT commands as usual. You may also generate a sources repository. To do that use the same procedure, but remember that you need to have the files .orig.tar.gz, .dsc and .diff.gz in the directory and you have to use Sources.gz instead of Packages.gz. The program used is also different. It is the dpkg-scansources. The command line will look like this:
dpkg-scansources debs | gzip > debs/Sources.gz
Notice that dpkg-scansources doesn't need an 'override' file. The sources.list's line is:
deb-src file:/root debs/"
Sometimes you have lots of packages .deb that you would like to use APT to install so that the dependencies would be automaticaly solved.
To do that create a directory and put the .debs you want to index in it . For example:
mkdir /root/debs
So, inside the directory /root, create an empty file, with any name. That is because an APT repository needs a file known as 'override', it may be empty, but it has to exist. One may use the following command to create this file:
touch file
Inside this file you may want to define some options to override the ones the ones that come with the package. It looks like follows:
package priority section
package is the name of the package, priority is low, medium or high and section is the section to which it belongs. It is enough to leave the file empty/
Still in the /root directory do:
dpkg-scanpackages debs file | gzip > debs/Packages.gz
In the above line, file is the 'override' file, the command generates a file debs/Packages.gz that contains various informations about the packages, which are used by APT. To use the packages, finally, add:
deb file:/root debs/
After that just use the APT commands as usual. You may also generate a sources repository. To do that use the same procedure, but remember that you need to have the files .orig.tar.gz, .dsc and .diff.gz in the directory and you have to use Sources.gz instead of Packages.gz. The program used is also different. It is the dpkg-scansources. The command line will look like this:
dpkg-scansources debs | gzip > debs/Sources.gz
Notice that dpkg-scansources doesn't need an 'override' file. The sources.list's line is:
deb-src file:/root debs/"
Web - Setting Joomla Directory Permissions
Web - Setting Joomla Directory Permissions: "Setting Joomla Directory Permissions
Topic: Web Posted:2006-08-13
Printer Friendly: Print
spacerspacer
The main thing that needs to be changed during a Joomla install is the directory permissions. Here is a shot of the install application before fixing the permissions:
administrator/backups Unwriteable
administrator/components Unwriteable
administrator/modules Unwriteable
administrator/templates Unwriteable
cache Unwriteable
components Unwriteable
images Unwriteable
images/banners Unwriteable
images/stories Unwriteable
language Unwriteable
mambots Unwriteable
mambots/content Unwriteable
mambots/editors Unwriteable
mambots/editors-xtd Unwriteable
mambots/search Unwriteable
mambots/system Unwriteable
media Unwriteable
modules Unwriteable
templates Unwriteable
Here is the sequence of commands to set the permissions for the web server account (apache):
chgrp apache administrator/backups
chgrp apache administrator/components
chgrp apache administrator/modules
chgrp apache administrator/templates
chgrp apache cache
chgrp apache components
chgrp apache images
chgrp apache images/banners
chgrp apache images/stories
chgrp apache language
chgrp apache mambots
chgrp apache mambots/content
chgrp apache mambots/editors
chgrp apache mambots/editors-xtd
chgrp apache mambots/search
chgrp apache mambots/system
chgrp apache media
chgrp apache modules
chgrp apache templates
chmod g+w administrator/backups
chmod g+w administrator/components
chmod g+w administrator/modules
chmod g+w administrator/templates
chmod g+w cache
chmod g+w components
chmod g+w images
chmod g+w images/banners
chmod g+w images/stories
chmod g+w language
chmod g+w mambots
chmod g+w mambots/content
chmod g+w mambots/editors
chmod g+w mambots/editors-xtd
chmod g+w mambots/search
chmod g+w mambots/system
chmod g+w media
chmod g+w modules
chmod g+w templates
Now the installation check looks like this:
administrator/backups Writeable
administrator/components Writeable
administrator/modules Writeable
administrator/templates Writeable
cache Writeable
components Writeable
images Writeable
images/banners Writeable
images/stories Writeable
language Writeable
mambots Writeable
mambots/content Writeable
mambots/editors Writeable
mambots/editors-xtd Writeable
mambots/search Writeable
mambots/system Writeable
media Writeable
modules Writeable
templates Writeable"
Topic: Web Posted:2006-08-13
Printer Friendly: Print
spacerspacer
The main thing that needs to be changed during a Joomla install is the directory permissions. Here is a shot of the install application before fixing the permissions:
administrator/backups Unwriteable
administrator/components Unwriteable
administrator/modules Unwriteable
administrator/templates Unwriteable
cache Unwriteable
components Unwriteable
images Unwriteable
images/banners Unwriteable
images/stories Unwriteable
language Unwriteable
mambots Unwriteable
mambots/content Unwriteable
mambots/editors Unwriteable
mambots/editors-xtd Unwriteable
mambots/search Unwriteable
mambots/system Unwriteable
media Unwriteable
modules Unwriteable
templates Unwriteable
Here is the sequence of commands to set the permissions for the web server account (apache):
chgrp apache administrator/backups
chgrp apache administrator/components
chgrp apache administrator/modules
chgrp apache administrator/templates
chgrp apache cache
chgrp apache components
chgrp apache images
chgrp apache images/banners
chgrp apache images/stories
chgrp apache language
chgrp apache mambots
chgrp apache mambots/content
chgrp apache mambots/editors
chgrp apache mambots/editors-xtd
chgrp apache mambots/search
chgrp apache mambots/system
chgrp apache media
chgrp apache modules
chgrp apache templates
chmod g+w administrator/backups
chmod g+w administrator/components
chmod g+w administrator/modules
chmod g+w administrator/templates
chmod g+w cache
chmod g+w components
chmod g+w images
chmod g+w images/banners
chmod g+w images/stories
chmod g+w language
chmod g+w mambots
chmod g+w mambots/content
chmod g+w mambots/editors
chmod g+w mambots/editors-xtd
chmod g+w mambots/search
chmod g+w mambots/system
chmod g+w media
chmod g+w modules
chmod g+w templates
Now the installation check looks like this:
administrator/backups Writeable
administrator/components Writeable
administrator/modules Writeable
administrator/templates Writeable
cache Writeable
components Writeable
images Writeable
images/banners Writeable
images/stories Writeable
language Writeable
mambots Writeable
mambots/content Writeable
mambots/editors Writeable
mambots/editors-xtd Writeable
mambots/search Writeable
mambots/system Writeable
media Writeable
modules Writeable
templates Writeable"
Techy Title Here: Benchmarking Untangle Gateway
This summary is not available. Please
click here to view the post.
Authenticate to Active Directory with Ubuntu
Authenticate to Active Directory with Ubuntu: "Authenticate to Active Directory with Ubuntu
Friday, 10 July 2009 08:04 John Ciacia
While Linux is a fantastic operating system, when it comes to user rights management, Active Directory is far superior than anything Linux currently implements. As a result many businesses and organizations implement the technology. For a longtime it was extremely difficult to get a Linux operating system to authenticate with active directory--configuring multiple services and managing to get them to work with each other, let alone work with Windows was a task best left for those with years of Linux administration experience. However, in recent years as Linux has become more user friendly, and it should be no surprise that authenticating with active directory has become easy too. In the past few days I have been working with an Open Source software called likewise-open which is in the official Ubuntu repositories. Below is a quick guide to getting started and some tips/issues I have found.
Authenticating with likewise-open 4.1 (from Ubuntu 8.04 Repository)
1. Install likewise-open
# sudo apt-get install likewise-open
2. Join the domain
# sudo domainjoin-cli join your.fqdn domain_admin
For example:
# sudo domainjoin-cli join example.com Administrator
REBOOT
3. Update rc.d
# sudo update-rc.d likewise-open defaults
4. 4. Start likewise-open
# sudo /etc/init.d/likewise-open start
Using the Default Domain with likewise-open 4.1
To use the default domain (and avoid using DOMAIN\user to login) append the following line to /etc/samba/lwiauthd.conf
winbind use default domain = yes
Authenticating with likewise-open 5.1 (from Ubuntu 9.04 Repository)
1. Install likewise-open5
# sudo apt-get install likewise-open5
2. Join the domain
# sudo domainjoin-cli join your.fqdn domain_admin
For example:
# sudo domainjoin-cli join example.com Administrator
REBOOT
3. Update rc.d
# sudo update-rc.d likewise-open defaults
4. Start likewise-open
# sudo /etc/init.d/lsassd start
Using the Default Domain with likewise-open 5.1
To use the default domain (and avoid using DOMAIN\user to login) uncomment the following line in /etc/likewise-open5/lsassd.conf
assume-default-domain = yes
Giving Domain Administrators sudo Privileges
Append the following line to /etc/sudoers
%your.fdqn\\domain^admins ALL=(ALL) ALL
Known Issues
* After rebooting the computer and logging in you are given the error “Domain Controller unreachable, using cached credentials instead. Network rsource may be unavailable.” Likewise does not start correctly. You have to login as a local admin and run the following command and then users will be able to login.
# sudo /etc/init.d/likewise-open restart
Issue seems to be resolved with likewise-open5
* If you are having issues authenticating wirelessly, make sure your wireless connection is established. In many instances, wireless will only connect after you login.
* Samba does not hide hidden windows shares
This article was reprinted with permission from John Ciacia's blog."
Friday, 10 July 2009 08:04 John Ciacia
While Linux is a fantastic operating system, when it comes to user rights management, Active Directory is far superior than anything Linux currently implements. As a result many businesses and organizations implement the technology. For a longtime it was extremely difficult to get a Linux operating system to authenticate with active directory--configuring multiple services and managing to get them to work with each other, let alone work with Windows was a task best left for those with years of Linux administration experience. However, in recent years as Linux has become more user friendly, and it should be no surprise that authenticating with active directory has become easy too. In the past few days I have been working with an Open Source software called likewise-open which is in the official Ubuntu repositories. Below is a quick guide to getting started and some tips/issues I have found.
Authenticating with likewise-open 4.1 (from Ubuntu 8.04 Repository)
1. Install likewise-open
# sudo apt-get install likewise-open
2. Join the domain
# sudo domainjoin-cli join your.fqdn domain_admin
For example:
# sudo domainjoin-cli join example.com Administrator
REBOOT
3. Update rc.d
# sudo update-rc.d likewise-open defaults
4. 4. Start likewise-open
# sudo /etc/init.d/likewise-open start
Using the Default Domain with likewise-open 4.1
To use the default domain (and avoid using DOMAIN\user to login) append the following line to /etc/samba/lwiauthd.conf
winbind use default domain = yes
Authenticating with likewise-open 5.1 (from Ubuntu 9.04 Repository)
1. Install likewise-open5
# sudo apt-get install likewise-open5
2. Join the domain
# sudo domainjoin-cli join your.fqdn domain_admin
For example:
# sudo domainjoin-cli join example.com Administrator
REBOOT
3. Update rc.d
# sudo update-rc.d likewise-open defaults
4. Start likewise-open
# sudo /etc/init.d/lsassd start
Using the Default Domain with likewise-open 5.1
To use the default domain (and avoid using DOMAIN\user to login) uncomment the following line in /etc/likewise-open5/lsassd.conf
assume-default-domain = yes
Giving Domain Administrators sudo Privileges
Append the following line to /etc/sudoers
%your.fdqn\\domain^admins ALL=(ALL) ALL
Known Issues
* After rebooting the computer and logging in you are given the error “Domain Controller unreachable, using cached credentials instead. Network rsource may be unavailable.” Likewise does not start correctly. You have to login as a local admin and run the following command and then users will be able to login.
# sudo /etc/init.d/likewise-open restart
Issue seems to be resolved with likewise-open5
* If you are having issues authenticating wirelessly, make sure your wireless connection is established. In many instances, wireless will only connect after you login.
* Samba does not hide hidden windows shares
This article was reprinted with permission from John Ciacia's blog."
Manage your Active Directory from Linux with adtool
Manage your Active Directory from Linux with adtool: "Manage your Active Directory from Linux with adtool
Active Directory is one of those Microsoft tools that so many have no choice but to use. Although I much prefer LDAP because it is so much easier to set up and manage. But for much of the enterprise world Active Directory is the tool used. Does this mean you are locked into managing Active Directory from a Windows machine? No. If you are a creature of the command line you can manage your AD from the Linux command line. It’s not that difficult and, in the end, will give you many more options to keep your AD server managed.
Of course it is not just a matter of working on the Linux end of things. There is one issue to settle on the MS end. You have to activate Secure LDAP on your AD Server. This process goes beyond the scope of this article, but the steps are pretty clear.
Enable SLDAP
Here are the steps to enable Secure LDAP on your Windows 2003 AD server (I will leave out the details):
1. Create an Active Directory domain controller certificate request.
2. Create a Certification Authority.
3. Sign the certificate request by the Certification Authority.
4. Export the root certificate Certification Authority.
5. Import the root certificate Certification Authority onto the Domain Controller.
6. Import the LDAP Server certificate onto the Domain Controller.
7. Set up the UMRA (LDAP Client) computer.
8. Verify Secure LDAPS using SSL.
Installing adtool
Fortunately adtool will be found in your distributions’ repositories. So all you have to do is follow these steps:
1. Fire up Synaptic (or whichever Add/Remove Software utility you use).
2. Do a search for “adtool” (no quotes).
3. Mark the results for installation.
4. Click Apply to install.
5. Close Synaptic.
Configuring adtool
This is a bit of configuration you need to handle before you can use adtool on your AD server. First create the file (if it doesn’t exist) /etc/adtool.cfg and add the following contents:
uri ldaps://YOUR.DOMAIN.HERE
binddn cn=Administrator,cn=Users,dc=domain,dc=tld
bindpw $PASSWORD
searchbase dc=domain,dc=tld
Where YOUR.DOMAIN.HERE is the actual address to your Active Directory server.
Where PASSWORD is the password for the AD user that has proper permissions to manage the AD server.
You will also need to make sure the following is in your /etc/ldap/ldap.conf file:
BASE dc=YOUR,dc=DOMAIN,dc=HERE
URI ldaps://YOUR.DOMAIN.HERE
TLS_REQCERT allow
Without the above configuration you will not be able to accept the SSL certificates from the server.
Basic usage
The basic usage of the adtool command is simple. Of course you will have to understand Active Directory in order to really understand the usage of this tool. Below I will give you samples of commands to handle the basic tasks for AD. Any information in ALL CAPS would be altered to fit your needs.
Create a new organizational unit:
adtool oucreate ORGANIZATION NAME ou=user,dc=DOMAIN,dc=COM
Add a user:
adtool useradd USER ou=ORGANIZATION ou=user,cd=DOMAIN,dc=COM
Set a user password:
adtool setpass USER PASSWORD
Unlock a user:
adtool unlock USER
Create a group
adtool groupcreate GROUP ou=user,cd=DOMAIN,dc=COM
Add a user to a group:
adtool groupadd allusers USER
Add an email address for the user:
adtool attributereplace USER mail EMAIL@ADDRESS
Final thoughts
We’ve only really scratched the surface of this powerful tool. But from this you should be able to see how easy adtool can be as well as how helpful it is."
Active Directory is one of those Microsoft tools that so many have no choice but to use. Although I much prefer LDAP because it is so much easier to set up and manage. But for much of the enterprise world Active Directory is the tool used. Does this mean you are locked into managing Active Directory from a Windows machine? No. If you are a creature of the command line you can manage your AD from the Linux command line. It’s not that difficult and, in the end, will give you many more options to keep your AD server managed.
Of course it is not just a matter of working on the Linux end of things. There is one issue to settle on the MS end. You have to activate Secure LDAP on your AD Server. This process goes beyond the scope of this article, but the steps are pretty clear.
Enable SLDAP
Here are the steps to enable Secure LDAP on your Windows 2003 AD server (I will leave out the details):
1. Create an Active Directory domain controller certificate request.
2. Create a Certification Authority.
3. Sign the certificate request by the Certification Authority.
4. Export the root certificate Certification Authority.
5. Import the root certificate Certification Authority onto the Domain Controller.
6. Import the LDAP Server certificate onto the Domain Controller.
7. Set up the UMRA (LDAP Client) computer.
8. Verify Secure LDAPS using SSL.
Installing adtool
Fortunately adtool will be found in your distributions’ repositories. So all you have to do is follow these steps:
1. Fire up Synaptic (or whichever Add/Remove Software utility you use).
2. Do a search for “adtool” (no quotes).
3. Mark the results for installation.
4. Click Apply to install.
5. Close Synaptic.
Configuring adtool
This is a bit of configuration you need to handle before you can use adtool on your AD server. First create the file (if it doesn’t exist) /etc/adtool.cfg and add the following contents:
uri ldaps://YOUR.DOMAIN.HERE
binddn cn=Administrator,cn=Users,dc=domain,dc=tld
bindpw $PASSWORD
searchbase dc=domain,dc=tld
Where YOUR.DOMAIN.HERE is the actual address to your Active Directory server.
Where PASSWORD is the password for the AD user that has proper permissions to manage the AD server.
You will also need to make sure the following is in your /etc/ldap/ldap.conf file:
BASE dc=YOUR,dc=DOMAIN,dc=HERE
URI ldaps://YOUR.DOMAIN.HERE
TLS_REQCERT allow
Without the above configuration you will not be able to accept the SSL certificates from the server.
Basic usage
The basic usage of the adtool command is simple. Of course you will have to understand Active Directory in order to really understand the usage of this tool. Below I will give you samples of commands to handle the basic tasks for AD. Any information in ALL CAPS would be altered to fit your needs.
Create a new organizational unit:
adtool oucreate ORGANIZATION NAME ou=user,dc=DOMAIN,dc=COM
Add a user:
adtool useradd USER ou=ORGANIZATION ou=user,cd=DOMAIN,dc=COM
Set a user password:
adtool setpass USER PASSWORD
Unlock a user:
adtool unlock USER
Create a group
adtool groupcreate GROUP ou=user,cd=DOMAIN,dc=COM
Add a user to a group:
adtool groupadd allusers USER
Add an email address for the user:
adtool attributereplace USER mail EMAIL@ADDRESS
Final thoughts
We’ve only really scratched the surface of this powerful tool. But from this you should be able to see how easy adtool can be as well as how helpful it is."
Saturday, August 1, 2009
Gnome - change vino server password
Gnome - change vino server password: "Gnome - change vino server password
This guide is based on a Fedora 9 install.
All commands are run from a user account and not root.
To check current vino server settings
cat ~/.gconf/desktop/gnome/remote_access/%gconf.xml
To change the current vino server password
NewPassword=`echo -n 'newpassword' | base64`
gconftool-2 --type string --set /desktop/gnome/remote_access/vnc_password $NewPassword
Restart the vino server
gconftool-2 -s -t bool /desktop/gnome/remote_access/enabled false
gconftool-2 -s -t bool /desktop/gnome/remote_access/enabled true"
This guide is based on a Fedora 9 install.
All commands are run from a user account and not root.
To check current vino server settings
cat ~/.gconf/desktop/gnome/remote_access/%gconf.xml
To change the current vino server password
NewPassword=`echo -n 'newpassword' | base64`
gconftool-2 --type string --set /desktop/gnome/remote_access/vnc_password $NewPassword
Restart the vino server
gconftool-2 -s -t bool /desktop/gnome/remote_access/enabled false
gconftool-2 -s -t bool /desktop/gnome/remote_access/enabled true"
Shell script to change password - LinuxQuestions.org
Shell script to change password - LinuxQuestions.org: "And now, I've found what does work for me, in my limited case of what I needed. If this solution works for you too, then here it is:
Code:
echo [passwd] > /tmp/[password file]
passwd --stdin [user] < [file with password]"
Code:
echo [passwd] > /tmp/[password file]
passwd --stdin [user] < [file with password]"
Create Users And Change Passwords With A Bash Script | HowtoForge - Linux Howtos and Tutorials
Create Users And Change Passwords With A Bash Script | HowtoForge - Linux Howtos and Tutorials: "Create Users And Change Passwords With A Bash Script
Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Submitted by fakrul (Contact Author) (Forums) on Fri, 2007-03-16 16:33. :: Linux
Create Users And Change Passwords With A Bash Script
These two scripts are very important for the system admin who regularly works with mail servers and somehow forgets to backup his system username and password! Let’s say somehow we lost the usernames and passwords of the mail server. In this case the admin has to manually create all the users and then change the passwords for all the users. Tedious job. Let’s make our life easier.
First create a file which contains all the user name. Something like this:
nurealam
nayeem
mrahman
farid
rubi
sankar
Save the file as userlist.txt. Now create the following bash file:
#!/bin/sh
for i in `more userlist.txt `
do
echo $i
adduser $i
done
Save the file and exit.
chmod 755 userlist.txt
Now run the file:
./userlist.txt
This will add all the users to the system. Now we have to change the passwords. Let's say we want username123 as password. So for user nayeem the password will be nayeem123, rubi123 for user rubi and so on.
Create another bash file as follows:
#!/bin/sh
for i in `more userlist.txt `
do
echo $i
echo $i'123' | passwd –-stdin '$i'
echo; echo 'User $username’s password changed!'
done
Run the file. All the passwords are changed."
Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Submitted by fakrul (Contact Author) (Forums) on Fri, 2007-03-16 16:33. :: Linux
Create Users And Change Passwords With A Bash Script
These two scripts are very important for the system admin who regularly works with mail servers and somehow forgets to backup his system username and password! Let’s say somehow we lost the usernames and passwords of the mail server. In this case the admin has to manually create all the users and then change the passwords for all the users. Tedious job. Let’s make our life easier.
First create a file which contains all the user name. Something like this:
nurealam
nayeem
mrahman
farid
rubi
sankar
Save the file as userlist.txt. Now create the following bash file:
#!/bin/sh
for i in `more userlist.txt `
do
echo $i
adduser $i
done
Save the file and exit.
chmod 755 userlist.txt
Now run the file:
./userlist.txt
This will add all the users to the system. Now we have to change the passwords. Let's say we want username123 as password. So for user nayeem the password will be nayeem123, rubi123 for user rubi and so on.
Create another bash file as follows:
#!/bin/sh
for i in `more userlist.txt `
do
echo $i
echo $i'123' | passwd –-stdin '$i'
echo; echo 'User $username’s password changed!'
done
Run the file. All the passwords are changed."
Changing password via a script - The solution
Changing password via a script - The solution: "Changing password via a script
Bookmark Bookmark & Share
Last update on October 29, 2008 06:44 AM by jak58
Published by jak58
Changing password via a script
*
o Method 1: passwd
o Method 2: chpasswd
Method 1: passwd
Conventionally the command use to change password on Linux based system is passwd
, the option related to this command is รข€“stdin ,an this is all done throughout a pipe.
echo -e 'new_password\nnew_password' | (passwd --stdin $USER)
Method 2: chpasswd
Another alternative is to use the chpasswd, explain as below:
echo 'password:name' | chpasswd
Note that the first method can be use to change psssword on Samba based system:
echo -e 'new_password\nnew_password' | (smbpasswd -a -s $USER)"
Bookmark Bookmark & Share
Last update on October 29, 2008 06:44 AM by jak58
Published by jak58
Changing password via a script
*
o Method 1: passwd
o Method 2: chpasswd
Method 1: passwd
Conventionally the command use to change password on Linux based system is passwd
, the option related to this command is รข€“stdin ,an this is all done throughout a pipe.
echo -e 'new_password\nnew_password' | (passwd --stdin $USER)
Method 2: chpasswd
Another alternative is to use the chpasswd, explain as below:
echo 'password:name' | chpasswd
Note that the first method can be use to change psssword on Samba based system:
echo -e 'new_password\nnew_password' | (smbpasswd -a -s $USER)"
Subscribe to:
Posts (Atom)