The purpose of those comands are to find the newest file in a directory acvrdind to system date, and it has to be recursively found in each directory.
The problem is that i want to list in a long format every found file, but the commands i use produce unexpected results ,so the output lists in a... (5 Replies)
I have the following statement in script:
find ${LANDING_FILE_DIR}${BTIME_FILENAME_PATTERN2} -print | while read file; do
...
done
When there are no files located by the find comand it returns:
"find: bad status-- /home/rnitcher/test/....." to the command line
How do I get control in... (3 Replies)
I want the output of the find command to be printed and also the total files found by it. Can someone help in this.
Obviously $ find . -type f | wc -l will not output the files found but only the count. I want both. There can be millions and trillions of files so dont want the output of find... (3 Replies)
Hi,
i'm currently writing a script which tidys up old files. When using the find command I found that some files were not being listed
/export/home/ops***/test: ls -l processed
total 0
-rw-rw-r-- 1 ops*** ****** 0 Apr 20 11:53 test99
/export/home/ops***/test: ls -l
total 4... (9 Replies)
Trying to locate files less than xx days old, throughout all directories/subdirectories, but excluding certain types of directories and files.
The directories I want to search all contain the same characteristic (dbdef, pldef, ghdef, etc), and there are subdirectories within that I need to... (2 Replies)
Hi, I am new in scripting, and I am currently working on a script that will look for other files in a certain directory and exclude some file type.
this works fine:Find_File2Exclude=`find ${paths} -maxdepth 1 -type f \( ! -iname '*.out' ! -iname '*.auc' ! -iname '*.cps' ! -iname '*.log' ! -iname... (4 Replies)
Hello Forum,
I'm using the following command to find all inactive kernels installed on my RHEL server:
$ rpm -qa | grep '^kernel-' |grep -vE `uname -r`
but the result is in two lines:
kernel-3.10.0-1062.1.1.el7.x86_64
kernel-3.10.0-1062.el7.x86_64
Is there a one line command I can... (3 Replies)
Discussion started by: greavette
3 Replies
LEARN ABOUT DEBIAN
knife-client
KNIFE-CLIENT(1) Chef Manual KNIFE-CLIENT(1)NAME
knife-client - Manage Chef API Clients
SYNOPSIS
knife client sub-command (options)
SUB-COMMANDS
Client subcommands follow a basic create, read, update, delete (CRUD) pattern. The Following subcommands are available:
BULK DELETE
knife client bulk delete regex (options)
Delete clients where the client name matches the regular expression regex on the Chef Server. The regular expression should be given as a
quoted string, and not surrounded by forward slashes.
CREATE
knife client create client name (options)
-a, --admin
Create the client as an admin
-f, --file FILE
Write the key to a file
Create a new client. This generates an RSA keypair. The private key will be displayed on STDOUT or written to the named file. The public
half will be stored on the Server. For chef-client systems, the private key should be copied to the system as /etc/chef/client.pem.
Admin clients should be created for users that will use knife to access the API as an administrator. The private key will generally be
copied to ~/.chef/client\_name.pem and referenced in the knife.rb configuration file.
DELETE
knife client delete client name (options)
Deletes a registered client.
EDIT
client edit client name (options)
Edit a registered client.
LIST
client list (options)
-w, --with-uri
Show corresponding URIs
List all registered clients.
REREGISTER
client reregister client name (options)
-f, --file FILE
Write the key to a file
Regenerate the RSA keypair for a client. The public half will be stored on the server and the private key displayed on STDOUT or written to
the named file. This operation will invalidate the previous keypair used by the client, preventing it from authenticating with the Chef
Server. Use care when reregistering the validator client.
SHOW
client show client name (options)
-a, --attribute ATTR
Show only one attribute
Show a client. Output format is determined by the --format option.
DESCRIPTION
Clients are identities used for communication with the Chef Server API, roughly equivalent to user accounts on the Chef Server, except that
clients only communicate with the Chef Server API and are authenticated via request signatures.
In the typical case, there will be one client object on the server for each node, and the corresponding client and node will have identical
names.
In the Chef authorization model, there is one special client, the "validator", which is authorized to create new non-administrative clients
but has minimal privileges otherwise. This identity is used as a sort of "guest account" to create a client identity when initially setting
up a host for management with Chef.
SEE ALSO knife-node(1)AUTHOR
Chef was written by Adam Jacob adam@opscode.com with many contributions from the community.
DOCUMENTATION
This manual page was written by Joshua Timberman joshua@opscode.com. Permission is granted to copy, distribute and / or modify this docu-
ment under the terms of the Apache 2.0 License.
CHEF
Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home
Chef 10.12.0 June 2012 KNIFE-CLIENT(1)