search for: otherfiles

Hello All, I'm trying to use vi commands instead of using the mouse. I open Gnome-Terminal I open a file : vi /home/jvermeulen/.ssh/id_dsa.pub I select the key with " V " ( visual line ) I type " y " to yank the selected line. I can now use :e otherfile.txt and paste the text in otherfile.txt This is the only way I succeed in copying text to another file in

I''d like to be able to generate the contents of a file resource based on the contents of another file resources. For example: File { "/tmp/myfile": source => "puppet:///mymodule/myfile", } File { "/tmp/otherfile": content =>generate_otherfile(File["/tmp/myfile"])), } in this case the generate_otherfile() function will use the resource

Ok, I''ve been reading and I have some questions about best practices: I understand that modules are to be self contained blocks that i can just drop in. Using best practices, how does this fit into the naming scheme? Classes are singletons. I think i understand this. I''ve been defining classes in /etc/puppet/classes, but then how does this relate to any modules i might want

I've been trying to figure out how to read in a large file for a few days now, and after extensive research I'm still not sure what to do. I have a large comma delimited text file that contains 59 fields in each record. There is also a header every 121 records This function works well for smallish records getcsv=function(fname){ ff=file(description = fname) x <- readLines(ff)

Joe Pfaltzgraff@PATAPSCO 03/21/2001 04:08 PM Here is the situation: /samba/users/personA/Phone.doc (0644) /samba/public/Phone.doc (symlink to above file) PersonB opens the Phone.doc in the public share with read-only access. PersonA wants to open the Phone.doc in their user area with full access in order to modify the file. However Word will only open the file read-only. When I check

Release Announcements ===================== This is the third release candidate of Samba 4.21.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.21 will be the next version of the Samba suite. UPGRADING ========= Hardening of "valid

Release Announcements ===================== This is the third release candidate of Samba 4.21.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.21 will be the next version of the Samba suite. UPGRADING ========= Hardening of "valid

Release Announcements ===================== This is the fourth release candidate of Samba 4.21.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.21 will be the next version of the Samba suite. UPGRADING ========= Hardening of "valid

Release Announcements ===================== This is the fourth release candidate of Samba 4.21.? This is *not* intended for production environments and is designed for testing purposes only.? Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.21 will be the next version of the Samba suite. UPGRADING ========= Hardening of "valid

Release Announcements --------------------- This is the first stable release of the Samba 4.21 release series. Please read the release notes carefully before upgrading. Hardening of "valid users", "invalid users", "read list" and "write list" ========================================================================= In previous versions of Samba, if a

Release Announcements --------------------- This is the first stable release of the Samba 4.21 release series. Please read the release notes carefully before upgrading. Hardening of "valid users", "invalid users", "read list" and "write list" ========================================================================= In previous versions of Samba, if a

...: Fname(BaseName), Fpath(DirName), Keep(KeepFile) { + Fpath = Fpath + "/" + BaseName; + Keep = true; +} + +IPOFile::~IPOFile() { + if (Keep) + sys::fs::remove(Fpath); +} + +IPOFileMgr::IPOFileMgr(): WorkDir("llvmipo") { + IRFiles.reserve(20); + ObjFiles.reserve(20); + OtherFiles.reserve(8); + KeepFiles = true; + WorkDirCreated = false; +} + +IPOFileMgr::~IPOFileMgr() { + if (!KeepFiles) { + uint32_t NumRm; + sys::fs::remove_all(Twine(WorkDir), NumRm); + } +} + +bool IPOFileMgr::CreateWorkDir(std::string &ErrorInfo) { + if (WorkDirCreated) + return true; +...