A collection of fields describing the shared content.
The title of the content being shared.
The description of the content being shared.
A fully qualified URL for the content being shared.
A fully qualified URL to a thumbnail image to accompany the shared content.
The image should be at least 80 x 150px for best results.
A comment by the member to associated with the share.
If none of the above content parameters are provided, the comment must contain a URL to the content you want to share. If the comment contains multiple URLs, only the first one will be analyzed for content to share.
A collection of visibility information about the share.
One of the following values:
anyone: Share will be visible to all members.
connections-only: Share will only be visible to connections of the member performing the share.
This field is required in all sharing calls.
Share on Company page has the same max length limit as above.
Encountered: $ sudo service ssh --full-restart * Stopping OpenBSD Secure Shell server sshd [ OK ] * Starting OpenBSD Secure Shell server sshd sshd: no hostkeys available -- exiting. Run ssh-keygen -A In the /etc/ssh/ folder, and then restart the server by: $ sudo service ssh --full-restart * Stopping OpenBSD Secure Shell server sshd [ OK ] * Starting OpenBSD Secure Shell server sshd [ OK ]
mv is the wrong tool for this job; you want cp and then rm . Since you're moving the file to another filesystem this is exactly what mv is doing behind the scenes anyway, except that mv is also trying to preserve file permission bits and owner/group information. This is because mv would preserve that information if it were moving a file within the same filesystem and mv tries to behave the same way in both situations. Since you don't care about the preservation of file permission bits and owner/group information, don't use that tool. Use cp --no-preserve=mode and rm instead. But if you don't care about the warning, mv actually does move the files before complaining ownership problem.