Restriction of adding links is too restrictive Post: 303019933

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...

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,...

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 ...

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?

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 ?

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: ...

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

LEARN ABOUT SUNOS

kitpost

KITSEND(1)                                                    General Commands Manual                                                   KITSEND(1)

NAME

       kitpost - posts distribution kits

SYNOPSIS

       kitpost [ -hrV ] [ -H file ] [ -D desc ] [ -m dest1,dest2 ] [ kits ] [ newsgroups ]

DESCRIPTION

       Kitpost  posts  distribution kits made by makedist to some (source) newsgroups specified on the command line. If you do not specify any kit
       list, then all the kits are sent. Otherwise, only the specified kits will be (re)sent.

       A kit list may include ranges, 1-10 specifying kits 1 through 10, and 5- meaning kits 5 up to the last one. You may also specify  kit  num-
       bers by separating them with commas or spaces, and even mix with ranges, such as: 1 3 5-7 9.

       Kitpost ensures correct References: lines are inserted in your postings so that all parts but the first point to the root article. Threaded
       newsreaders and end-users traditionally appreciate that.

OPTIONS

       The following options are recognized by kitpost:

       -h        Print help message and exit.

       -m dest1,destn
                 Sends kits by e-mail to the specified recipients. This option may be used in conjunction with newsgroup  posting.  It  is  mainly
                 intended  for  sites  where  direct  posting to a moderated newsgroup is not allowed by inews. You may thus send your kits to the
                 newsgroup moderator in a form that will ease the whole posting process.

       -r        Signals a repost.

       -D description
                 Specify a description string that will be added to the subject line. Usually a brief sentence (less than, say, 40 characters).

       -H file   Specify a file to be used as header introduction in the first part of your posting. Usually the root README file.

       -V        Print version number and exit.

BUGS

       Article cross-referencing is properly set-up only when the whole package is (re)posted in one batch.

       It is not currently possible to set-up the article headers manually or better, interactively.

AUTHOR

       Raphael Manfredi <ram@hptnos02.grenoble.hp.com>

SEE ALSO

       makedist(1), kitsend(1).

                                                                        ram                                                             KITSEND(1)