Sponsored Content
Top Forums Shell Programming and Scripting Copy files with pattern from ext4 to cifs file system Post 302851939 by cero on Tuesday 10th of September 2013 05:53:01 AM
Old 09-10-2013
MS-Windows does not allow filenames with colons.
This User Gave Thanks to cero For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Copy a file from a dvd to the local AIX file system

Hi, I am a newbie to AIX, so please bear with me. I have mounted a dvd drive on AIX. I am trying to copy the file that is on the dvd drive on to the local machine. However, I get an error: cp: c1m_0001.gz: A system call received a parameter that is not valid. Can some one point me to the... (1 Reply)
Discussion started by: anurag1510
1 Replies

2. Filesystems, Disks and Memory

ext4 - ready for production system?

Gidday, Are you using ext4 for production system? Or is it better to opt for a more conservative strategy, like ext3 for instance? What are your experiences? Thanks in advance, Loïc. (3 Replies)
Discussion started by: Loic Domaigne
3 Replies

3. Shell Programming and Scripting

CIFS file system check.

I have written a script to take backup of linux data on window's shared folder. I have used following method in my script. mount -t cifs <windowshare> -o username=username,password=myPassword <mountlocation> However most of linux system doesnt support CIFS filesystem. How would i check if... (7 Replies)
Discussion started by: pinga123
7 Replies

4. Shell Programming and Scripting

copy, then delete lines in file with sed using a pattern

I need to copy lines to a new file from files with sed using a pattern in char postions 1-3. Then after the copy, I need to delete those same lines from the input files. For example, string "ABC" in pos 1-3 (6 Replies)
Discussion started by: laksjfhoius9123
6 Replies

5. AIX

Copy huge files system

Dear Guy’s By using dd command or any strong command, I’d like to copy huge data from file system to another file system Sours File system: /sfsapp File system has 250 GB of data Target File system: /tgtapp I’d like to copy all these files and directories from /sfsapp to /tgtapp as... (28 Replies)
Discussion started by: Mr.AIX
28 Replies

6. Shell Programming and Scripting

Search the pattern and copy in to the file

my qn is i have one file hex.txt.it contains some junk data and some hexa valueslike hex.txt sdfjhjkh 0x1233jkfhgjfhgajk;gha 0xacdd jkgahfjkgha;sjghajklgha;gh aghfjkgh;a 0xccc jhfjkhsd ox23cd 0x456 jkhdfjhjkafh like this now iwant a script like to separate the hex values and paste into the... (12 Replies)
Discussion started by: siva.hardwork
12 Replies

7. Shell Programming and Scripting

Copy/print all lines between pattern is found in .log files

Hi, I have a folder with multiple (< 33) .log files. And I have to copy the lines between two patterns from all the .log files to a new file. (script file with a loop?) Thanks in advance. 1.log ... .. xx1> begin ... .. .. >>> Total: 2 Alarms .. .. (17 Replies)
Discussion started by: AK47
17 Replies

8. Shell Programming and Scripting

Copy data to new file based on input pattern

Hi All, I want to create a new file based on certain conditions and copy only those conditioned data to new file. Input Data is as it looks below. ORDER|Header|Add|32|32|1616 ORDER|Details1......... ORDER|Details2......... ORDER|Details3......... ORDER|Details4............ (10 Replies)
Discussion started by: grvk101
10 Replies

9. UNIX for Beginners Questions & Answers

Copy pattern inside the file

Hi all, I have files and have a missing record. I need copy the existing record and mark those values up. For example in the below file 11048 is missing. I need to copy 22001 and copy those create the values for 11048. I have 120 set of files and I need to do that on all files. Note the... (8 Replies)
Discussion started by: arunkumar_mca
8 Replies
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)
All times are GMT -4. The time now is 07:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy