search for: groupn

...e 4 directories: /path/to/sync/common/ <- common files /path/to/sync/group1/ <- group1 specific only /path/to/sync/group2/ <- group2 specific only /path/to/sync/group3/ <- group3 specific only Then I'd run an rsync like: rsync -av --overlay /path/to/sync/groupN \ /path/to/sync/common remotehost: Thinking in terms of a list of files to be transferred, I would like: - Anything present in common/ added to the file list; then - Anything present in groupN/ added to the list, clobbering if applicable (regardless of mtime) - The destination directory to sh...

Just two clarifying questions about the package "pcse". Argument "groupN": It should be a factor that tells us to what subgroup each record belongs, right? Argument "groupT" should be a vector that contains the time identifier. Can it be just a factor (e.g., 1, 2, 3, etc.) - or does it have to be in the date format? Thank you very much! -- Dimitri Lia...

...frame is organized in pooled times series fashion, but with various missing values along the spacial and temporal dimension. library(pcse) tmodel<-lm(var1 ~ var2 + var3 + var4 + as.factor(year) , data=dataframe.2, na.action="na.exclude") pcse.tmodel<-pcse(tmodel, groupN = country, groupT = year, pairwise=TRUE) Error in pcse(tmodel, groupN = country, groupT = year, pairwise = TRUE) : Length of groupN and groupT must equal nrows of using data. I have checked the length of groupN, groupT and the residuals of tmodel, only to find out they are equally lo...

...sync/common/ <- common files > /path/to/sync/group1/ <- group1 specific only > /path/to/sync/group2/ <- group2 specific only > /path/to/sync/group3/ <- group3 specific only > > Then I'd run an rsync like: > rsync -av --overlay /path/to/sync/groupN \ > /path/to/sync/common remotehost: > > Thinking in terms of a list of files to be transferred, I would like: > - Anything present in common/ added to the file list; then > - Anything present in groupN/ added to the list, clobbering if applicable (regardless of mtime) > - T...

In <B4E1EC5D-5E46-4A98-9018-C5E4C4441712 at equalit.ie>, on 03/31/16 at 03:40 PM, tomr <tom at equalit.ie> said: Hi, >Then I'd run an rsync like: > rsync -av --overlay /path/to/sync/groupN \ > /path/to/sync/common remotehost: >Thinking in terms of a list of files to be transferred, I would like: - >Anything present in common/ added to the file list; then - Anything >present in groupN/ added to the list, clobbering if applicable >(regardless of mtime) - The destina...

...common files >> /path/to/sync/group1/ <- group1 specific only >> /path/to/sync/group2/ <- group2 specific only >> /path/to/sync/group3/ <- group3 specific only >> >> Then I'd run an rsync like: >> rsync -av --overlay /path/to/sync/groupN \ >> /path/to/sync/common remotehost: >> >> Thinking in terms of a list of files to be transferred, I would like: >> - Anything present in common/ added to the file list; then >> - Anything present in groupN/ added to the list, clobbering if applicable (regardless...

...aps SAM aliases in any domain to real unix groups "domain group map" - maps SAM groups in any domain to real unix groups note that "any domain" currently means "only the domain the SAMBA server is either a member of or responsible for". the syntax of entries is: unixgroupname [DOMAIN\]ntgroupname unixgroupname [DOMAIN\]ntaliasname where [DOMAIN\] is currently unsupported. if [DOMAIN\] is unspecified, then the default is either the domain for which the samba server is a controller (security = user) or the domain of which the samba server is a member (security = doma...

...; (@users)=split(' ',$grline[3]); > if (grep(/^$username$/,@users)) { > push(@groups,$grline[0]); > } > } > # Uncomment to debug > #print "$username belongs to:n"; > #foreach $group (@groups) { > # print "$groupn"; > #} > > So, @groups is a list that contains all the group names that the > user belongs to. See changes to your code below. > > > > > Then the logon script is set to :%u.bat > > > > It works great with the only problem being with users belonging t...

Dear all I am looking for a solution for a module to define alle possible user and then install the one or more user from that module if needed on a server, but not all of them. My idea is something like this. Can I define a user in the nodes.pp at a special Server to install that user? init.pp class admin_user::group { group { "group1": gid => "888",