Showing posts with label configuration. Show all posts
Showing posts with label configuration. Show all posts
Sunday, September 10, 2017
Unable to load Deep Freeze Configuration Login Program will not be available
Unable to load Deep Freeze Configuration Login Program will not be available
Problem: No Deep Freeze Icon in Taskbar

To Solve This Issue Disable All Faronics Deep Freeze Services
You can done this by simply typing the command services.msc in the run dialog box. Once you are in the services window, locate the service name DFserv and right click on it and select properties (refer to image below).

After clicking properties, stop and disable the service. Refer to the image below for instructions. Note: Restart is needed for changes to take effect on your system.

After restarting, at this point you no longer have any Deep Freeze service or application running at the background of your system. Also the system Deep Freeze Icon should be gone. You are still able re-enable Deep Freeze by reversing the whole process. Note: You can now uninstall deep freeze and re install again.
More Tags: Angry Bird, Blogger, Fate , Plants Vs Zombie, Special Force, Point Blank, Ai Maps, Deep Freeze UnFreezer, Ninja Saga, Deep Freeze, Samsung SGH, Guitar Pro, USB XP Install, Yahoo 443 Problem, Turtle Odyssey, GTA San-Andreas, PlayStation, Tips Tweaks Tricks, HTML, Facebook, Animated JPG, Counter-Strike, USB Windows Format, Screensaver, USB Security.
download file now
Tuesday, September 5, 2017
Tutorial Installation and Configuration FTP Server in Linux Ubuntu Using ProFTPd
Tutorial Installation and Configuration FTP Server in Linux Ubuntu Using ProFTPd
ProFTPd is an application that used to transfer data or familiar called as FTP (File Transfer Protocol). By using proFTPd, we can create an FTP server that can make a server can provide facilities to upload and download from the server.
ProFTPd is easy to configure. This step-by-step installation and configuration FTP server using proFTPd.
Installation ProFTPd:
- Install proftpd with the following command:
sudo apt-get install proftpd
- While the installation process, you are given two options to running proFTPd from inetd or standalone. If FTP traffic is large, you must choose standalone. You mus create FTP user with the following commands for edit file:
sudo nano /etc/shells
Then add the following code:/bin/false
Then create folder/directory what you want to share using FTP, for example: /home/ShareFTP. So you must type this command to create that directory:sudo mkdir /home/ShareFTP
- Create user and password with type this command:
sudo useradd name_user -p password_user -d /home/ShareFTP -s /bin/false
*name_user is username for account FTP server. password_user is password of that username. - Then create download and upload directory into ShareFTP with the following command:
sudo mkdir /home/ShareFTP/download
sudo mkdir /home/ShareFTP/upload
- Setting permission directory for user with the following command:
sudo chmod 755 /home/ShareFTP
sudo chmod 755 /home/ShareFTP/download
sudo chmod 755 /home/ShareFTP/upload
Configuration ProFTPd:
- Edit configuration file /etc/proftpd/proftpd.conf using nano editor with this following way:
sudo nano /etc/proftpd/proftpd.conf
- Will display the text editor of proftpd configuration, then put your cursor on the bottom line. Then add this script:
<Anonymous /home/ShareFTP/>
User nama_user
Group nogroup
UserAlias anonymous ftp
DirFakeUser on ftp
DirFakeGroup on ftp
RequireValidShell off
MaxClients 10
DisplayLogin welcome.msg
DisplayChdir .message
<Directory *>
<Limit WRITE>
AllowAll
</Limit>
</Directory>
</Anonymous> - Save and restart proftpd service with the following command:
sudo /etc/init.d/proftpd restart
- Configuration proFTPd has been completed. For transfer file from windows to linux server, you can run an application FileZilla, then fill with this configuration:
hostname: alamat IP server
username: username FTP
password: password user FTP
port : 21
or you can type ftp localhost in linux Terminal, then type username and password.
download file now
Thursday, August 24, 2017
Tweaking dhcp client configuration to change the default DNS servers to Open DNS
Tweaking dhcp client configuration to change the default DNS servers to Open DNS
The DNS servers of my ISP is always behaving erratically. The DNS look up times are abysmally large and some times I get an address not found error while browsing. On ubuntu/debian systems the DNS servers are specified in /etc/resolv.conf. I tried to edit /etc/resolv.conf and put open dns servers as default DNS servers. But, my ISP supplies their DNS server address along with IP address for the system via DHCP. Every time my system renews its DHCP lease. my /etc/resolv.conf is also rewritten with their DNS address.
My /etc/resolv.conf ( supplied by ISP) looks like this.
$ cat /etc/resolv.conf
domain asianetindia.com
search asianetindia.com
nameserver 202.88.238.3
nameserver 202.88.238.5
nameserver 202.88.231.2
There is a trick I used to make Open DNS servers as my default DNS server.
Edit /etc/dhcp3/dhclient.conf and look for the line.
#prepend domain-name-servers 127.0.0.1;
Add the following line immediately below the above line.
prepend domain-name-servers 208.67.222.222;
prepend domain-name-servers 208.67.220.220;You can also put any other DNS servers.
Now renew the lease with
$ sudo dhclient eth0
The new /etc/resolve.conf looks like this.
$ cat /etc/resolv.conf
domain asianetindia.com
search asianetindia.com
nameserver 208.67.220.220
nameserver 208.67.222.222
nameserver 202.88.238.3
nameserver 202.88.238.5
nameserver 202.88.231.2
DNS look up is made from open dns.
download file now
Sunday, August 6, 2017
trivial Jenkins configuration
trivial Jenkins configuration
Knowing when your software breaks is useful. If you catch subtle errors soon after the change, its *much* easier to figure out which bit of code "optimization" broke things for the users.
Another benefit is fixing "works for me" syndrome. Even if youre building software just for yourself, its nice to have a 3rd party to verify that you didnt do silly things. Forgetting to check in South database changes is quite easy, but that simple omission will break everything.
Jenkins is a cranky to set up, because its a collection of moving parts. The best setup would be having Jenkins rebuild your tests every time GitHub detects a source code change.
The following setup is not as geeky, but its much, much easier: tell Jenkins copy local source files and test, every now and then.
- go to Jenkins on your local computer: http://localhost:8080/
- New Job ("free-style software project")
- Youre now on the Configure page. click Add Build Step.
- Execute Shell
- adjust Makefile to your liking
- run the test every few minutes
For #4, in the Command area, type this little script:
rsync -av --delete --exclude=.git MYSOURCEDIR $WORKSPACE
make -C $WORKSPACE test
Replace MYSOURCEDIR with your source directory -- the full path. For me its /home/johnm/work/yed. The above copies source from your normal development area to the job-specific Jenkins area. It strips files that have been deleted in the source tree
In step #5, put a Makefile with a "test" verb in the top of your source code. Im running Django, so to test the project I want to run the Django test suite on my main app.
test:
./manage.py test -v1
Remember to use the TAB key instead of spaces on the 2nd line.
At this stage, test your Jenkins job. On the Job screen click Configure on the left to return to the Configuration page. Edit the job, but dont press Save at the bottom of the page -- press Apply. Open your job in a second browser window. Click Build Now to start the job, wait for a few seconds, then click the new link which appears in the Build History section of the page.
If its not perfect, go back to the Configuration page, make changes, press Apply; switch to the Project browser window, click Build Now again. This workflow lets you rapidly make changes to your Jenkins project without having lots of windows open.
Step 6: Once #1-5 above is working to your satisfaction, you can automate the test. On the Job Configure screen, in the Build Triggers section, enable "Build periodically". In the text area, type this schedule:
H/15 * * * *
This means run your test every 15 minutes, no matter if anything has changed or not. The "H" is to not overwhelm your system if lots of tests are running at once.
As an alternate for #5, just to make sure things are running, you can use the following Makefile instead:
test:
echo out of beer! ; false
When you run the Jenkins job on this, the test will fail because the "false" command returns a status of 1. This proves that Jenkins sees your code, is copying to the right place, and is running your Makefile test command.
download file now
Labels:
configuration,
jenkins,
trivial
Subscribe to:
Posts (Atom)