Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators Restriction of adding links is too restrictive Post 303019923 by drkirkby on Tuesday 10th of July 2018 08:27:20 AM
Old 07-10-2018
Restriction of adding links is too restrictive

I am trying to write a shell script that generates links to a website. Not to spam it. The code necessarily adds things that are links, and so get rejected.

In the end I have up, and have not written the post.

Whilst I apprecaite you want to avoid spam, could you not implement something so any page with a link has a noindex, nofollow, and advise people that links will not be followed?

Apache often often runs on unix systems, and people will want to write scripts that do things related to Apache and websites.

Also, the Google capture thing is getting very hard for a human. Often 1% of a screen sign for example will be in one square.

I know spammers are a problem, but the restrictions make this site unusable for me.
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Restriction for more than one user

How do l restrict more than one users on a multiple programming environment using the c shell profile. That is if a user is log-on on one terminal the system should be able to prompt a message if the users attempt to log on on another terminal. I user openserver 5.0.4 with dummy terminals, and also... (7 Replies)
Discussion started by: kayode
7 Replies

2. Solaris

FTP Restriction

I have a senario and i wonder how to do it ? i used NcFTPd and i dont think its applicable using that application or i didnt know how to configure it. i want to have a user for FTP that user is only restricted to put and get from a certain directory and all sub-directories for that directory,... (0 Replies)
Discussion started by: mduweik
0 Replies

3. UNIX for Advanced & Expert Users

Restrictive mail implementation problem

Any tips on this problem will be greatly appreciated. I need to build a Linux mailserver, that needs to meet the following requirements: 3 usergroups: endusers, supervisors, and management Endusers will be on a local Linux mailserver Supervisors and management will be on Google Apps ... (0 Replies)
Discussion started by: zefflyn
0 Replies

4. Solaris

Hard Links and Soft or Sym links

When loooking at files in a directory using ls, how can I tell if I have a hard link or soft link? (11 Replies)
Discussion started by: Harleyrci
11 Replies

5. AIX

List all the soft links and hard links

Hi I'm logged in as root in an aix box Which command will list all the soft links and hard links present in the server ? (2 Replies)
Discussion started by: newtoaixos
2 Replies

6. Shell Programming and Scripting

AWK Restrictive Search

I have a file with most of the lines formatted in this way: testaccount:D#%G%^V&:MeMyselfandI:memyselfandi@somesite.com:11/242012:192.168.1.1,192.168.1.2,192.168.1.3,192.168.1.4,192.168.1.5 There are a few lines with: ... (2 Replies)
Discussion started by: metallica1973
2 Replies

7. Solaris

Sudo -s restriction

Is there a way to stop users envoking a root shell with sudo on Solaris 10. I want users to use sudo <cmd> but not sudo -s (5 Replies)
Discussion started by: u20sr
5 Replies
LN(1)							    BSD General Commands Manual 						     LN(1)

NAME
ln -- make links SYNOPSIS
ln [-fhinsv] source_file [target_file] ln [-fhinsv] source_file ... target_dir DESCRIPTION
The ln utility creates a new directory entry (linked file) which has the same modes as the original file. It is useful for maintaining mul- tiple copies of a file in many places at once without using up storage for the ``copies''; instead, a link ``points'' to the original copy. There are two types of links: hard links and symbolic links. How a link ``points'' to a file is one of the differences between a hard or symbolic link. The options are as follows: -f Unlink any already existing file, permitting the link to occur. -h If the target_file or target_dir is a symbolic link, do not follow it. This is most useful with the -f option, to replace a symlink which may point to a directory. -i Cause ln to write a prompt to standard error if the target file exists. If the response from the standard input begins with the char- acter 'y' or 'Y', then unlink the target file so that the link may occur. Otherwise, do not attempt the link. (The -i option over- rides any previous -f options.) -n Same as -h, for compatibility with other ln implementations, namely GNU coreutils. -s Create a symbolic link. -v Cause ln to be verbose, showing files as they are processed. By default ln makes hard links. A hard link to a file is indistinguishable from the original directory entry; any changes to a file are effective independent of the name used to reference the file. Hard links may not normally refer to directories and may not span file sys- tems. A symbolic link contains the name of the file to which it is linked. The referenced file is used when an open(2) operation is performed on the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2) must be done to obtain information about the link. The readlink(2) call may be used to read the contents of a symbolic link. Symbolic links may span file systems and may refer to directories. Given one or two arguments, ln creates a link to an existing file source_file. If target_file is given, the link has that name; target_file may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified, the link will be made to the last component of source_file. Given more than two arguments, ln makes links in target_dir to all the named source files. The links made will have the same name as the files being linked to. SEE ALSO
link(2), lstat(2), readlink(2), stat(2), symlink(2), symlink(7) STANDARDS
The ln utility conforms to IEEE Std 1003.2-1992 (``POSIX.2''). The -v option is an extension to IEEE Std 1003.2-1992 (``POSIX.2''). HISTORY
A ln utility appeared in Version 6 AT&T UNIX. BSD
October 29, 2007 BSD
All times are GMT -4. The time now is 06:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy