Yes, unfortunately documentation is usually the weakest part. If anyone on the list is a good technical writer, enjoys doing such, and is interested in getting more involved, please let us know. We are definitely in need of someone to assist in the documentation.
Thanks, Aaron On Fri, Oct 18, 2013 at 3:18 PM, Curtis <[email protected]> wrote: > On Fri, Oct 18, 2013 at 12:52 PM, Dmitri Chebotarov <[email protected]> wrote: >> Hi >> >> You could try >> >> grep '|<req_id>:<res_id>|image|' /var/log/vcld.log | grep ssh >> >> This would show all ssh commands that vcld ran during on the image during >> imaging Š > > Thanks Dmitri. That's a good idea. It would be great if what VCL is > doing to an image to create a new image was documented somewhere other > than the code. > > Thanks, > Curtis. > >> >> -- >> Thank you, >> >> Dmitri Chebotarov >> VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & >> Messaging >> 223 Aquia Building, Ffx, MSN: 1B5 >> Phone: (703) 993-6175 | Fax: (703) 993-3404 >> >> >> >> >> >> >> >> On 10/18/13 13:45 , "Curtis" <[email protected]> wrote: >> >>>How do I determine what commands are run by VCL on an >>>vm/instance/computer/etc when creating a new image from an existing >>>image? >>> >>>Thanks, >>>Curtis. >>> >>>-- >>>Twitter: @serverascode >>>Blog: serverascode.com >> > > > > -- > Twitter: @serverascode > Blog: serverascode.com -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
