search for: write_only

...------------------------------------------------ diff -urN rsync-2.5.2.orig/loadparm.c rsync-2.5.2/loadparm.c --- rsync-2.5.2.orig/loadparm.c Sun Dec 2 09:16:15 2001 +++ rsync-2.5.2/loadparm.c Sat Feb 23 13:48:12 2002 @@ -117,6 +117,7 @@ char *comment; char *lock_file; BOOL read_only; + BOOL write_only; BOOL list; BOOL use_chroot; BOOL transfer_logging; @@ -149,6 +150,7 @@ NULL, /* comment */ DEFAULT_LOCK_FILE, /* lock file */ True, /* read only */ + False, /* write only */ True, /* list */ True, /* use chroot */ False, /* transfer logging */ @@ -265,6 +267,7...

...file_list *flist; char *dir = argv[0]; + extern int module_id; extern int relative_paths; extern int recurse; if (verbose > 2) rprintf(FINFO,"server_sender starting pid=%d\n",(int)getpid()); + if (am_daemon && lp_write_only(module_id) && !am_sender) { + rprintf(FERROR,"ERROR: module is write only\n"); + exit_cleanup(RERR_SYNTAX); + return; + } + if (!relative_paths && !push_dir(dir, 0)) { rprintf(FERROR, "push_di...

...tion 'kex_free_newkeys': kex.h:116:18: note: destination object 'name' of size 8 116 | char *name; | ^~~~ /usr/include/bits/string_fortified.h:66:6: note: in a call to function '__explicit_bzero_chk' declared with attribute 'access (write_only, 1, 2)' 66 | void __explicit_bzero_chk (void *__dest, size_t __len, size_t __destlen) Not sure if this is a real problem or not but I thought I'd pass it over just in case. Chris

...tFile::READ_ONLY)); std::cout << "my-ups description: " << config.getDescription("my-ups") << std::endl; // ... config.setDriver("my-ups", "snmp-ups"); config.writeTo(nut::NutFile( "/usr/local/ups/etc/ups.conf", nut::NutFile::WRITE_ONLY)); Regards, vasek -- V?clav Krpec Network UPS Tools project Eaton Opensource Team ----------------------------- Eaton Elektrotechnika s.r.o. ~ S?dlo spolecnosti, jak je zaps?no v rejstr?ku: Kom?rovsk? 2406, Praha 9 - Horn? Pocernice, 193 00, Cesk? Republika ~ Jm?no, m?sto, kde byla spolecnos...

...end + + if !spec.config.key?(:read_only) && !spec.config[:read_only] != ''true'' + write_connection_pool[active_connection_name][spec.object_id] = spec if !write_connection_pool[active_connection_name][spec.object_id] + end + if !spec.config.key?(:write_only) && !spec.config[:write_only] != ''true'' + read_connection_pool[active_connection_name][spec.object_id] = spec if !read_connection_pool[active_connection_name][spec.object_id] + end + @@defined_connections[spec.object_id] = spec + end + + def self...

Hi, This is a proof of concept of GPU forwarding for Linux guest on Linux host. I'd like to get comments and suggestions from community before I put more time on it. To summarize what it is: 1. It's a solution to bring GPU acceleration for Linux vm guest on Linux host. It could works with different GPU although the current proof of concept only works with Intel GPU. 2. The basic idea