Will the output file be opened and closed several times?

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Dup2 - for file descriptor opened by a different process

is it possible to duplicate file descriptors(opened by a different process) with the help of dup or dup2. the two process do not share parent child relationship as well.

2. Shell Programming and Scripting

File exists, but cannot be opened.How to check- whether it could be opened to read when it exists

Hi #Testing for file existence if ; then echo 'SCHOOL data is available for processing' else echo 'SCHOOL DATA IS NOT AVAILABLE FOR PROCESSING' : i wrote a script, where it begins by checking if file exists or not. If it exists, it truncates the database...

3. Shell Programming and Scripting

Help with cp command when destination file is opened

I am writing a shell script (runs on HP Unix) which copies files from a source directory to another destination daily. The destination directory always have the files with same name as in the source directory. And daily a new file will be created in the source. cp command works fine if the file...

4. Shell Programming and Scripting

How to find who opened/modified a file last

Hi *, I'm wondering if it possible to know WHO opened or modified a file last? I know it's possible with some options of find and also ls to get when the file was modified last. I'm currently supervising a file and have to log all users name who opened or modified it. Thanx a lot for any...

5. Shell Programming and Scripting

Output section of file between two expressions multiple times

Attached is the exact ouput of a vmware VDR log file I am working with but what I am trying to achieve is as follows: I need to output sections of the file using the string "Normal backup" as the start and "Duration" as the end to seperate files so I can then manipulate them further to create...

6. Shell Programming and Scripting

Find process through file opened

Hello all, I have a file that is growing and growing by the action of any process. How can I find what process is? Thank you

7. UNIX for Advanced & Expert Users

My command is still running but someone closed my shell, can I get my output still?

I ran an fs_usage (based off dtrace facility) but someone closed the window I think.. But I still see the process running # 15023 I tried fg 15023 but it told me no job control.. Is there anyway I can see my output? The scan has been running an hour and the output is valuable to me.

8. UNIX for Advanced & Expert Users

same file being opened by two users at a time

I want to avoid a situation where because two users simultaneously open a file and modify and save, leaving the original file in mess. Is there a way in UNIX to warn a user if that particular file is already being used by another user. Thanks in advance

9. Shell Programming and Scripting

How to recognize if a file still opened by any process?

Is there a way to tell for sure if a file currently is opened by any running process? I have a task to filter a text file which is produced by some long process. I have no way to communicate with that process, but I have access to a location, where that proces produce an output file. Need...

10. Programming

maximum number of times - a file can be opened

Hi All, We can find the maximum of open file descriptors in hold with respect to a process. As default size was 256 (with getrlimit) and the hard limt was 65536 I tried changing the limit to 1024(with setrlimit) successfully changed the limit but still I couldnt have as many open file...

LEARN ABOUT NETBSD

dd-list

DD-LIST(1)						      General Commands Manual							DD-LIST(1)

NAME

       dd-list - nicely list .deb packages and their maintainers

SYNOPSIS

       dd-list [-hiusV] [--help] [--stdin] [--sources Sources_file] [--dctrl] [--version] [--uploaders] [package ...]

DESCRIPTION

       dd-list produces nicely formatted lists of Debian (.deb) packages and their maintainers.

       Input is a list of source or binary package names on the command line (or the standard input if --stdin is given).  Output is a list of the
       following format, where package names are source packages by default:

	      J. Random Developer <jrandom@debian.org>
		     j-random-package
		     j-random-other

	      Diana Hacker <diana@example.org>
		     fun-package
		     more-fun-package

       This is useful when you want, for example, to produce a list of packages that need to attention from their maintainers, e.g., to be rebuilt
       when a library version transition happens.

OPTIONS

       -h, --help
	      Print brief help message.

       -i, --stdin
	      Read package names from the standard input, instead of taking them from the command line. Package names are whitespace delimited.

       -d, --dctrl
	      Read  package  list  from standard input in the format of a Debian package control file. This includes the status file, or output of
	      apt-cache. This is the fastest way to use dd-list, as it uses the maintainer information from the input instead of  looking  up  the
	      maintainer of each listed package.

	      If no Source: line is given, the Package: name is used for output, which might be a binary package name.

       -s, --sources Sources_file
	      Read package information from the specified Sources_files.  This can be given multiple times.

	      If no Sources_files are specified, any files matching /var/lib/apt/lists/*_source_Sources will be used.

       -u, --uploaders
	      Also  list  developers  who  are named as uploaders of packages, not only the maintainers; this is the default behaviour, use --nou-
	      ploaders to prevent it. Uploaders are indicated with "(U)" appended to the package name.

       -nou, --nouploaders
	      Only list package Maintainers, do not list Uploaders.

       -b, --print-binary
	      Use binary package names in the output instead of source package names (has no effect with --dctrl if  the  Package:  line  contains
	      source package names).

       -V, --version
	      Print the version.

AUTHOR

       Lars Wirzenius <liw@iki.fi>

       Joey Hess <joeyh@debian.org>

Debian								    2011-10-27								DD-LIST(1)

Shell Programming and Scripting