Sponsored Content
Full Discussion: cp -R behaviour
Top Forums Shell Programming and Scripting cp -R behaviour Post 302278636 by cfajohnson on Tuesday 20th of January 2009 07:27:56 PM
Old 01-20-2009

Use the same code for both FreeBSD and Linux:

Code:
cp -Rv "$sourcee" "$destination"

Other varieties may not have the -v option.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Count behaviour when using su -

Gentlemen, OK, I have an odd issue here perhaps someone can shed some light for me. When running a script as its user/owner the below pause/wait works just fine. When a developer has used su - to assume the username the pause does not happen... This is a HPUX11.00 machine, I have copied the blurb... (1 Reply)
Discussion started by: Eronysis
1 Replies

2. Programming

Different behaviour of this program

Hi, I have one doubt, in the below program, if I declare char *b inside the main(), the function compiles & runs properly. But at the same time, if I declare it globally it compiles but when we run it, it creates core dump (segmentation fault) both in C & C++. It is not being trapped by catch... (7 Replies)
Discussion started by: royalibrahim
7 Replies

3. Shell Programming and Scripting

A Strange Behaviour!!!

Can some-one give me a view to this : I have a directory in an unix server, having permissions r-xr-xr-x .This directory is basically a source directory. Now there is another directory basically the destination directory which has all the permissions. Note:I log in as not the owner,but user... (5 Replies)
Discussion started by: navojit dutta
5 Replies

4. Shell Programming and Scripting

Why this behaviour of IF condition?

I have a variable, defndata, which is a number (fetched from a file using awk). I want that if defndata is not initialized (that is its not found in the file using awk), then to execute a block of statements, otherwise execute another block. if then .... else ... fi Now this... (4 Replies)
Discussion started by: indianjassi
4 Replies

5. UNIX for Advanced & Expert Users

eval behaviour

Hi, I have snippet like the following x="1" prompt1="hi" if I say eval echo \$prompt$x then it is giving o/p "hi" if I say `eval echo \$prompt$x` here it is giving 1 ! if I add one more escape character i.e. `eval echo \\$prompt$x` then it is giving "hi" Can you please... (3 Replies)
Discussion started by: shahnazurs
3 Replies

6. Ubuntu

Weird rm behaviour

I am little bit confused by the behaviour of rm in Ubuntu. It seems that as a regular user I can delete files owned by another user even when the permissions are set to 644. Here is an example: cjohnson@carbon:~/test$ sudo touch testfile cjohnson@carbon:~/test$ ls -al total 8 drwxr-xr-x... (2 Replies)
Discussion started by: ccj4467
2 Replies

7. Programming

different behaviour in fg and bg

fg = foreground bg = background I have a cobol program that I start with a very simple script. The script is not at fault as it has not changed and the program worked in fg and bg before. I have altered the logging in the program and moved my cursor declare to working storage. The program runs... (6 Replies)
Discussion started by: Bruble
6 Replies

8. Programming

Sort behaviour

I see strange results when sorting with -n options and I wander if somebody can explain it. Input file and two results: $ cat aa 14 -1 11 -1 0 -1 0 $ sort -u aa -1 0 (1 Reply)
Discussion started by: migurus
1 Replies

9. Red Hat

Ps command different behaviour

Hi Experts, ps command behavior in Redhat is such that it outputs all the output(of long lengths). In Unix the ps command output was limited to only 80 chars. In that if you pipe its output to another command hen the 80 chars restriction wouldn't be there. This 80 char limitation will only be... (14 Replies)
Discussion started by: Albert_Pinto7
14 Replies
FREEBSD-UPDATE.CONF(5)					      BSD File Formats Manual					    FREEBSD-UPDATE.CONF(5)

NAME
freebsd-update.conf -- configuration file for freebsd-update(8) DESCRIPTION
The freebsd-update.conf file controls the behaviour of the freebsd-update(8) utility. The file contains lines consisting of a case-sensitive option name and zero or more parameters. Empty lines and any part of a line following a '#' character are ignored. Unless stated otherwise, specifying an option multiple times is an error. The possible options and their meanings are as follows: KeyPrint The single parameter following this keyword is the SHA256 hash of the RSA key which will be trusted to sign updates. ServerName The single parameter following this keyword is the name of the server or server pool from which updates will be downloaded. Components The parameters following this keyword are the components or sub-components of FreeBSD which will be updated. The components are ``src'' (source code), ``world'' (non-kernel binaries), and ``kernel''; the sub-components are the individual distribution sets generated as part of the release process (e.g., ``src/base'', ``src/sys'', ``world/base'', ``world/catpages'', ``kernel/smp''). Note that prior to FreeBSD 6.1, the ``kernel'' component was distributed as part of ``world/base''. This option can be specified multiple times, and the parameters accumulate. IgnorePaths The parameters following this keyword are regular expressions; updates to paths which start with a string matching one of these regular expressions will be ignored. This option can be specified multiple times, and the parameters accumulate. IDSIgnorePaths The parameters following this keyword are regular expressions; paths which start with a string matching one of these regular expressions will be ignored by "freebsd-update IDS". This option can be specified multiple times, and the parameters accumulate. UpdateIfUnmodified The parameters following this keyword are regular expressions; updates to paths which start with a string matching one of these regular expressions will be ignored if the files have been modified locally (unless they are merged -- see MergeChanges below). This option can be specified multiple times, and the parameters accumulate. MergeChanges The parameters following this keyword are regular expressions; updates to paths which start with a string matching one of these regular expressions will be merged with local modifications. This option can be specified multiple times, and the parameters accumulate. WorkDir The single parameter following this keyword is the directory in which temporary files and downloaded updates will be stored. MailTo The single parameter following this keyword is the address to which cron output will be mailed. AllowAdd The single parameter following this keyword must be ``yes'' or ``no'' and specifies whether freebsd-update is allowed to create new files, directories, and symlinks if these are part of updates downloaded. Note that freebsd-update will not re-add files which have been deleted from a FreeBSD installation unless those files were previously added as part of an update. AllowDelete The single parameter following this keyword must be ``yes'' or ``no'' and specifies whether freebsd-update is allowed to delete files, directories, and symlinks as part of updates downloaded. KeepModifiedMetadata The single parameter following this keyword must be ``yes'' or ``no'' and specifies whether freebsd-update should keep existing file ownership, permissions, and flags when installing updates if these have been modified locally. StrictComponents The single parameter following this keyword must be ``yes'' or ``no'' and specifies whether freebsd-update should interpret the list of components of FreeBSD specified via the Components option strictly as a list of components installed which should be upgraded when the upgrade command is used ("yes"), or merely as a list of components which might be installed, of which freebsd-update should identify which in fact are present ("no"). BackupKernel The single parameter following this keyword must be ``yes'' or ``no'' and specifies whether freebsd-update will cre- ate a backup of the old kernel before installing a new kernel. This backup kernel can be used to recover a system where the newly installed kernel somehow did not work. Note that the backup kernel is not reverted to its original state by the freebsd-update rollback command. BackupKernelDir This keyword sets the directory which is used to store a backup kernel, if the BackupKernel feature is enabled. If the directory already exist, and it was not created by freebsd-update, the directory is skipped. In the case of the primary directory name not being usable, a number starting with '1' is appended to the directory name. Like with the primary directory name, the constructed directory name is only used if the path name does not exist, or if the directory was previously created by freebsd-update. If the constructed directory still exist the appended number is incremented with 1 and the directory search process restarted. Should the number increment go above 9, freebsd-update will abort. BackupKernelSymbolFiles The single parameter following this keyword must be ``yes'' or ``no'' and specifies whether freebsd-update will also backup kernel symbol files, if they exist. The kernel symbol files takes up a lot of disk space and are not needed for recovery purposes. If the symbol files are needed, after recovering a system using the backup kernel, the freebsd-update rollback command will recreate the symbol files along with the old kernel. FILES
/etc/freebsd-update.conf Default location of the freebsd-update configuration file. SEE ALSO
sha256(1), freebsd-update(8) AUTHORS
Colin Percival <cperciva@FreeBSD.org> FreeBSD August 19, 2009 FreeBSD
All times are GMT -4. The time now is 04:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy