Check your configuration as follows:
$ shopt
...
huponexit off
...
$
As you can see, `huponexit` is `off`. So you don't have to use `nohup` in this case.
Sunday, December 20, 2015
Friday, December 18, 2015
AdSense is not showing up on Blogspot
If you set up AdSense on Blogspot but ADs are not showing up,
wait a few minutes.
For me, it was blanks but after a few minutes ADs shows up.
wait a few minutes.
For me, it was blanks but after a few minutes ADs shows up.
Deploy a jar file to Maven repository in Gradle
To deploy a jar file to Maven repository in Gradle,
add the following configuration to `build.gradle`:
apply plugin: 'maven'
repositories {
mavenLocal()
jcenter()
maven { url "http://repo.izeye.com:8080/repository/internal" }
}
uploadArchives {
repositories {
mavenDeployer {
repository(url: "http://repo.izeye.com:8080/repository/internal") {
authentication(userName: "admin", password: "1234")
}
}
}
}
If you encounter the following error:
Could not find metadata :test/maven-metadata.xml in remote (http://repo.izeye.com:8080/repository/internal)
make sure you added it to `repositories`.
Reference:
https://docs.gradle.org/current/userguide/maven_plugin.html
add the following configuration to `build.gradle`:
apply plugin: 'maven'
repositories {
mavenLocal()
jcenter()
maven { url "http://repo.izeye.com:8080/repository/internal" }
}
uploadArchives {
repositories {
mavenDeployer {
repository(url: "http://repo.izeye.com:8080/repository/internal") {
authentication(userName: "admin", password: "1234")
}
}
}
}
If you encounter the following error:
Could not find metadata :test/maven-metadata.xml in remote (http://repo.izeye.com:8080/repository/internal)
make sure you added it to `repositories`.
Reference:
https://docs.gradle.org/current/userguide/maven_plugin.html
Tuesday, December 15, 2015
rsync: failed to connect to 1.2.3.4: Connection refused (111)
If you encounter the following error:
$ rsync -avr 1.2.3.4::I/home/izeye/test/ .
rsync: failed to connect to 1.2.3.4: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6]
$
checkout your rsync configuration as follows:
$ sudo vi /etc/xinetd.d/rsync
service rsync
{
disable = yes
flags = IPv6
socket_type = stream
wait = no
user = root
server = /usr/bin/rsync
server_args = --daemon
log_on_failure += USERID
}
and change `disable` from `yes` to `no`.
Restart the xinetd as follows:
$ sudo /etc/init.d/xinetd restart
As a side note, if you encounter the following error:
$ rsync -avr 1.2.3.4::I/home/izeye/test/ .
@ERROR: access denied to I from unknown (5.6.7.8)
rsync error: error starting client-server protocol (code 5) at main.c(1503) [receiver=3.0.6]
$
checkout your `/etc/rsyncd.conf`, especially `hosts allow` and `hosts deny` values.
$ rsync -avr 1.2.3.4::I/home/izeye/test/ .
rsync: failed to connect to 1.2.3.4: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6]
$
checkout your rsync configuration as follows:
$ sudo vi /etc/xinetd.d/rsync
service rsync
{
disable = yes
flags = IPv6
socket_type = stream
wait = no
user = root
server = /usr/bin/rsync
server_args = --daemon
log_on_failure += USERID
}
and change `disable` from `yes` to `no`.
Restart the xinetd as follows:
$ sudo /etc/init.d/xinetd restart
As a side note, if you encounter the following error:
$ rsync -avr 1.2.3.4::I/home/izeye/test/ .
@ERROR: access denied to I from unknown (5.6.7.8)
rsync error: error starting client-server protocol (code 5) at main.c(1503) [receiver=3.0.6]
$
checkout your `/etc/rsyncd.conf`, especially `hosts allow` and `hosts deny` values.
rm: cannot unlink `/c/Users/izeye/IdeaProjects/impression-neo/.git/rebase-merge/.git-rebase-todo.swp': Permission denied
If you encounter the following error during aborting rebase:
C:\Users\izeye\IdeaProjects\impression-neo>git rebase --abort
rm: cannot unlink `/c/Users/izeye/IdeaProjects/impression-neo/.git/rebase-merge/.git-rebase-todo.swp': Permission denied
rm: cannot remove directory `/c/Users/izeye/IdeaProjects/impression-neo/.git/rebase-merge': Directory not empty
C:\Users\izeye\IdeaProjects\impression-neo>
Kill `vim.exe`.
C:\Users\izeye\IdeaProjects\impression-neo>git rebase --abort
rm: cannot unlink `/c/Users/izeye/IdeaProjects/impression-neo/.git/rebase-merge/.git-rebase-todo.swp': Permission denied
rm: cannot remove directory `/c/Users/izeye/IdeaProjects/impression-neo/.git/rebase-merge': Directory not empty
C:\Users\izeye\IdeaProjects\impression-neo>
Kill `vim.exe`.
Force to push a specifc branch to origin in Git
To force to push a specifc branch to origin in Git,
do as follows:
git push -f origin gh-1004
Reference:
http://stackoverflow.com/questions/11453807/force-push-current-branch
do as follows:
git push -f origin gh-1004
Reference:
http://stackoverflow.com/questions/11453807/force-push-current-branch
Subscribe to:
Posts (Atom)