501 2346 564 0 2:20下午 ttys005 0:00.00 sh ./cread.sh
ssh dynamic forward 后台运行
$ ssh -T -D 1080 email@example.com </dev/null &  2665 ~/blog on master! choe@MBP⌚ 14:33:12 $ Last failed login: Fri Nov 24 06:33:09 UTC 2017 from 192.168.145.21 on ssh:notty There were 4667 failed login attempts since the last successful login.
If a background process tries to read from the terminal, it will be stopped. This is normal terminal and shell behavior. Only foreground processes are allowed to control the terminal like that.
To prevent it from reading from the terminal, run it with nohup to prevent it from accessing the terminal. This will redirect stdout/stderr automatically, but NOT redirect stdin , while stdout and stderr will be saved to a file in the current directory.
man hup NAME nohup – invoke a utility immune to hangups
SYNOPSIS nohup [–] utility [arguments]
DESCRIPTION The nohup utility invokes utility with its arguments and at this time sets the signal SIGHUP to be ignored. If the standard output is a terminal, the standard output is appended to the file nohup.out in the current directory. If standard error is a terminal, it is directed to the same place as the standard output.
Some shells may provide a builtin nohup command which is similar or identical to this utility. Consult the builtin(1) manual page.
tar 不支持in-place更新文件！ To pull your file from your archive, you can use tar xzf archive.tar.gz my/path/to/file.txt. Note that the directories in the file’s path will be created as well. Use tar t (i.e. tar tzf archive.tar.gz) to list the files in the archive.
tar does not support “in-place” updating of files. However, you can add files to the end of an archive, even if they have the same path as a file already in the archive. In that case, both copies of the file will be in the archive, and the file added later will override the earlier one. The command to use for this is tar r (or tar u to only add files that are newer than the archive) is the command to use. The . in the path should not be a problem.
There is a catch, though: you can’t add to a compressed archive. So you would have to do:
tar rf archive.tar data/data/com.myapp.backup/./files/settings.txt
Which is probably not what you want to hear, since it means rewriting the entire archive twice over. If it’s not a very large archive, it might be better to untar the whole thing and then re-tar it after editing. Alternately, you could use an uncompressed archive.
gzip -dc archive.tar.gz | tar -r data/data/com.myapp.backup/./files/settings.txt | gzip >archive_new.tar.gz
The Markdown syntax doesn’t provide one with the ability to control the position of an image.
In fact, it would be borderline against the Markdown philosophy to allow such formatting, as stated in the “Philosophy” section
“A Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. “
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
This works just fine: <img align="..." src="..." alt="...">
<p align="center"> <img /> </p>
didn't worked to me in GitHub. <p align="center"><img src="image" /></p> nor <p style="align:center"><img src="image" /></p> Original markdown processes markdown syntax within span tags. So some thing like the following should work: <span style="display:block;text-align:center">![Test Automation]Automated-Testing.png)</span> <img src="url" alt="alt text" width="whatever" height="whatever"> <a href="https://your-image-url.type"><img src="https://your-image-url.type" width="100" height="100"/></a> <div style="text-align:center"><img src="..." /></div>
language: zh-CN timezone: Asia/Shanghai note: Asia\Shanghai cause error: TypeError: Cannot read property ‘offset’ of null generate blog: https://hexo.io/docs/commands.html
Hexo provides a fast and easy deployment strategy. You only need one single command to deploy your site to your servers. $ hexo deploy Before your first deployment, you will have to modify some settings in _config.yml. A valid deployment setting must have a type field. For example: Git Install hexo-deployer-git. $ npm install hexo-deployer-git –save Edit settings. deploy: type: git repo: firstname.lastname@example.org:cuiwm/cuiwm.github.io.git # branch: master message: [message]
$ hexo new page “tags” INFO Created: ~/blog/source/tags/index.md
$ hexo new draft “My First Blog Post” creates -> ./source/_drafts/My-First-Blog-Post.md
The stuff between the dashes — at the top of the markdown file is called “front-matter”. It is metadata that is used by Hexo and the active theme. See the Hexo documentation on Front-Matter for more information. Ensure that your Markdown content for the page sits BELOW the front-matter dashes — or the content will not display (and you’ll likely see a YAMLException error in the server output).
Saving changes to your Markdown files will be automatically detected by the running hexo server and regenerated as static HTML files, but you must refresh the browser to view the changes.
If you dislike having to manually refresh the browser each time, the hexo-livereload or hexo-browsersync plugins can do it automatically.
To install the hexo-browsersync plugin (my personal favorite):