10-11-2019
no issues but as I said we just reinstalled them a couple of weeks ago to 3.1.0.21 so they are latest and greatest. But so far chef is doing a great job updating the root password, /etc/resolv.conf and other files to our standards - and it has not yet killed a box
I am not sure how a 2000 day old VIOS would behave (not to mention that I am pretty sure that version is no longer supported by IBM since a while anyways - what do you have, 2.5.x?. Do you have any physical box with similar old OS you could try if it would generally work for that OS version? I am more of a chef user, so all I do is install the client software and run it and check afterwards that the initial run did what it was supposed to do
7 More Discussions You Might Find Interesting
1. AIX
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
2. AIX
Hi,
I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server,
is there any command by using which from vio server I can reboot vio client? (3 Replies)
Discussion started by: manoj.solaris
3 Replies
3. AIX
Hi,
I am having single p series blade with Single Physcial CPU with dual core,
on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor,
My query using which command it will... (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. AIX
Hi
I am facing very strange issue on my vio server 5 vio clients are confgured, now I am to connect 3 vio client , i am unable to connect 2 vio client my ip address,subnet mask,gateway is correct.
i have rebooted and reconfigured the ip address, but issue is persists.
Kindly suggest how to... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
5. AIX
Hi
im logged in to the vio servers now.
when i give
# lspv | wc -l
i get the count as 6246
how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ? (1 Reply)
Discussion started by: newtoaixos
1 Replies
6. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
7. AIX
Hi
In my vio server I have the below output
$ lsvopt | grep -i SAPSITGS
sapsitgs_cdrom TL12UP.iso 3182
In my vio client lpar I have the below output
root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server
cd1... (1 Reply)
Discussion started by: newtoaixos
1 Replies
LEARN ABOUT DEBIAN
chef-client
CHEF-CLIENT(8) Chef Manual CHEF-CLIENT(8)
NAME
chef-client - Runs a client node connecting to a chef-server.
SYNOPSIS
chef-client (options)
-S, --server CHEFSERVERURL
The chef server URL
-c, --config CONFIG
The configuration file to use
-d, --daemonize
Daemonize the process
-g, --group GROUP
Group to set privilege to
-i, --interval SECONDS
Run chef-client periodically, in seconds
-j, --json-attributes JSON_ATTRIBS
Load attributes from a JSON file or URL
-E, --environment ENVIRONMENT
Set the Chef Environment on the node
-l, --log_level LEVEL
Set the log level (debug, info, warn, error, fatal)
-L, --logfile LOGLOCATION
Set the log file location, defaults to STDOUT - recommended for daemonizing
-V, --verbose
Ensures logging goes to STDOUT as well as to other configured log location(s).
-N, --node-name NODE_NAME
The node name for this client
-o, --override-runlist
Replace current run list with specified items
-K, --validation_key KEY_FILE
Set the validation key file location, used for registering new clients
-k, --client_key KEY_FILE
Set the client key file location
-s, --splay SECONDS
The splay time for running at intervals, in seconds
-u, --user USER
User to set privilege to
-P, --pid PIDFILE
Set the PID file location, defaults to /tmp/chef-client.pid
--once Cancel any interval or splay options, run chef once and exit
-v, --version
Show chef version
-h, --help
Show this message
DESCRIPTION
The Chef Client is where almost all of the work in Chef is done. It communicates with the Chef Server via REST, authenticates via Signed
Header Authentication, and compiles and executes Cookbooks.
A Chef Client does work on behalf of a Node. A single Chef Client can run recipes for multiple Nodes.
Clients are where all the action happens - the Chef Server and Chef Expander are largely services that exist only to provide the Client
with information.
SEE ALSO
Full documentation for Chef and chef-client is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.
AUTHOR
Chef was written by Adam Jacob adam@ospcode.com of Opscode (http://www.opscode.com), with contributions from the community. This manual
page was written by Joshua Timberman joshua@opscode.com with help2man. Permission is granted to copy, distribute and / or modify this docu-
ment under the terms of the Apache 2.0 License.
On Debian systems, the complete text of the Apache 2.0 License can be found in /usr/share/common-licenses/Apache-2.0.
Chef 10.12.0 June 2012 CHEF-CLIENT(8)