Restricted File Creation for particuler pattern


 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory Restricted File Creation for particuler pattern
# 1  
Old 10-23-2009
Restricted File Creation for particuler pattern

HI All, I have this wierd requirment. Any help will be appriciated.

I need to restrict file creation with certain pattern. Suppose, i want my system not to allow creation of files with *.exe extension. The requirment is that file should not be created like it happen in windows you can't create file with name "com, lpr etc etc" same thing i need in unix/linux..i want to create a rule saying that this system will not accept any file name ending with *.exe and *.txt.

Please advice..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to print the specific part of the file name with file creation date?

Hello Folks, I have an requirement, where i need to get total count of the file based on creation date with there filename selected pattern. Filename: MobileProtocol.20171228T154200.157115.udr I want to get the count of files created on each day based on a pattern find. find . -type... (7 Replies)
Discussion started by: sadique.manzar
7 Replies

2. UNIX Desktop Questions & Answers

Restricted shell with execution permission on a file

Hi, I've created a user which shell is the restricted one (/usr/lib/rsh), but I've realized that the user cannot execute a script !!! The scope was to allow the ssh access to a user that could not access to any other directories but there that user should be able to run a script that retrieves ... (2 Replies)
Discussion started by: mary0
2 Replies

3. Shell Programming and Scripting

Big pattern file matching within another pattern file in awk or shell

Hi I need to do a patten match between files . I am new to shell scripting and have come up with this so far. It take 50 seconds to process files of 2mb size . I need to tune this code as file size will be around 50mb and need to save time. Main issue is that I need to search the pattern from... (2 Replies)
Discussion started by: nitin_daharwal
2 Replies

4. UNIX for Dummies Questions & Answers

List the directories, having given pattern in the directories name, sorted by creation date

It is for HP-Unix B.11.31. Requirement: 1. List the directories, having given pattern in the directories name, sorted by creation date. Example: Directories with name "pkg32*" or "pkg33*" 2. On the output of 1. list the directories by creation date as sort order, with creation date... (2 Replies)
Discussion started by: Siva SQL
2 Replies

5. Shell Programming and Scripting

Restricted File Comparison

Hey guys, I've got a scripting problem that has been bugging me so thought I'd ask the wise people here! Basically I have two overlapping log files, and I want to get the newest lines from the new log file that aren't in the old log file - but not the old lines in the old log that aren't in the... (1 Reply)
Discussion started by: salamagd
1 Replies

6. Shell Programming and Scripting

File creation

Hi I need to write a file with value value from Paramer which is passed from datastage. It should overwrite the file if already exists. Can anybody provide command for this? (1 Reply)
Discussion started by: cnrj
1 Replies

7. Shell Programming and Scripting

Help with creating a text file in perl with file creation date.

Hi, I am quite new to Perl scripting and i need to create a .TXT file using perl, with fields (A,B,C,D,E), and this text file should be named with current file creation date "XYZ_CCYYMMDD.TXT" (i.e.XYZ_2011042514:33 PM). Can anyone who has done this, please share their expertise on this... (5 Replies)
Discussion started by: msrahman
5 Replies

8. Solaris

gzip a file and append creation date stamp to file

I want to gzip a file and append the creation date to the end of the file. How can I accomplish this task. Basically they are log files which need a creation date stamp appended to make sure they do not overwrite other log files. -jack (3 Replies)
Discussion started by: jacktravine
3 Replies

9. UNIX for Advanced & Expert Users

file creation

Hi, Is there any way to restrict directories with one type of file creation. regards. (8 Replies)
Discussion started by: guguli
8 Replies

10. Linux

creation of a file

how to create a file with the same modification time as another file is having using the copy command? (1 Reply)
Discussion started by: infyanurag
1 Replies
Login or Register to Ask a Question
coreadm(1M)															       coreadm(1M)

NAME
coreadm - core file administration SYNOPSIS
pattern] pattern] option] option] [pid...] [pid...] [arguments] [pid...] DESCRIPTION
The command is used for user space application core file management by specifying the name and the location of core files for abnormally terminating processes. See core(4). The command can be used to control system wide and process specific core file placement. The path and pattern is used by the operating system when generating a core file. The first form shown in can be used to control system wide core file settings or specify a pattern for init(1M). System administration privilege is required to change global core file settings. Global core file setting, including the setting for init(1M), is preserved across system reboot. Non-privileged users can change per-process core file settings for processes owned by that user. The real or the effective user ID of the calling process must match the real or the saved user ID of the receiving process unless the effective user ID of the calling process is a user who as appropriate privileges. A core file name pattern is a normal file system path name with embedded variables, specified with a leading character, that are expanded from values in effect when a core file is generated by the operating system. An expanded pattern over will be truncated to The possible pattern variables are: Options The following options are supported for Disable or enable the specified core file option. The and options can only be exercised with root privilege. The valid options for and are: Allow (or disallow) core dumps using the global core pattern. Allow (or disallow) core dumps using the per-process core pattern. Allow (or disallow) core dumps using the global core pattern for processes. Allow (or disallow) core dumps using the process core pattern for processes. Set the global core file name pattern to pattern. The pattern must start with an absolute path name which exists and can contain any of the special % variables described in the section. This option can only be exercised by the super-user. This is identical to specifying a per-process pattern only that the setting is applied to init(1M) and is preserved across reboot. Set the per-process core file name pattern to pattern for each of the specified process-ID's. The pattern can contain any of the special variables described in and need not begin with If it does not begin with the core file name will be evaluated relative to the current working directory at the time of core file creation. This option can be used by non-privileged users to specify core file settings for processes owned by that user. Super-users can apply it to any process. The per-process core file will be inherited by the future child processes of the affected pro- cesses. See fork(2). This option, when invoked without a PID will apply the settings to the calling process (usually the invoking shell). This option is used in conjunction with The option will execute the command specified with the per-process pattern that was specified with This option can be used to enable or disable core file creation for the target process. As an example, a user may choose to add the disable in the shell startup script to avoid creation of core files by that user. EXAMPLES
The following examples assume that the user has appropriate privilege. 1. To examine the current core file settings: $ coreadm global core file pattern: init(1M) core file pattern: global core dumps: disabled per-process core dumps: enabled global setid core dumps: disabled per-process setid core dumps: disabled 2. Set global core file settings to include process-ID and machine name and place the core file in the location $ coreadm -e global -g /mnt/cores/core.%p.%n A process with PID 1777 on the machine breaker will generate a core file in as (in addition to the core file generated in the CWD of PID 1777). 3. Examine the per process core file settings for process-IDs 1777 and 1778 $ coreadm 1777 1778 1777: core.%p.%u 1778: /nethome/gandalf/core/core.%f.%p.%t 4. A user can disable creation of core files completely by specifying in the shell startup file (for example, $ coreadm -P disable $$ $ coreadm $$ 1157: (Disabled) WARNINGS
The output format of may change without notice. Applications parsing the output, should not rely on the compatibility of the output format between releases. SEE ALSO
umask(1), init(1M), coreadm(2), core(4). coreadm(1M)

Featured Tech Videos