search for: osuse

Hint #1, to do any useful transformations on your variables you will probably need to convert them temporarily into character variables (aka strings). Do that with as.character(n$OSUSE) Probably your will want to convert each of the variables that are in this format into a set of numeric variables. Something like this: n <- data.frame(OSUSE = c("1","1,3","1,2,3")) n$OSUSE.Windows <- sapply( strsplit(n$OSUSE, ",") , function(X)...

...[ ]Windows [ ]Macinotsh [ ]Unix ...then the data exported for three different responses might look like ;1; ;1,3; ;1,2,3; ...where ";" is the field delimiter. I use read.table to get the data in. I read all the survey data into a table "n" and the field above is called "OSUSE". When I query R about the field, it tells me it is class "factor" > class(n$OSUSE) [1] "factor" > mode(n$OSUSE) [1] "numeric" I'd like to be able to do some simple things like: what is the most common item checked (1, 2, or 3?) What is the average num...

...ing 4.2.2 member server. Adding "require strong key = no" and "client NTLMv2 auth = no" to the member servers smb.conf but it did not change anything. Here is the log file on the dedicated member server of one client trying to connect my member server: SID for local machine OSUSE-TEST is: S-1-5-21-1853263269-3041869306-167322181 SID for domain MYDOM is: S-1-5-21-290147797-1639656955-1287535205 Join to 'MYDOM' is OK [2015/07/06 08:02:46.342573, 3] ../source3/smbd/oplock.c:1306(init_oplocks) init_oplocks: initializing messages. [2015/07/06 08:02:46.342706, 3] .....

Thanks for your reply, Rowland Penny <rowlandpenny241155 at gmail.com> wrote on 06.07.2015 10:03:20: > > In the first 2 lines of the log I see the SIDs dumped. > > Both for my domain and for my member server. > > > > SID for local machine OSUSE-TEST is: > > S-1-5-21-1853263269-3041869306-167322181 > > SID for domain MYDOM is: S-1-5-21-290147797-1639656955-1287535205 > > Join to 'MYDOM' is OK > > > > According to my LDAP the sid for my test member server (OSUSE-TEST) > > should be S-1-5-21-...

...your reply, > > Rowland Penny <rowlandpenny241155 at gmail.com> wrote on 06.07.2015 > 10:03:20: > > > > In the first 2 lines of the log I see the SIDs dumped. > > > Both for my domain and for my member server. > > > > > > SID for local machine OSUSE-TEST is: > > > S-1-5-21-1853263269-3041869306-167322181 > > > SID for domain MYDOM is: S-1-5-21-290147797-1639656955-1287535205 > > > Join to 'MYDOM' is OK > > > > > > According to my LDAP the sid for my test member server (OSUSE-TEST) > >...

...max log size = 500 name resolve order = host bcast unix extensions = No hide dot files = No csc policy = disable strict locking = No wide links = Yes [testshare] comment = test path = /testshare read only = No inherit permissions = Yes I joined the machine (osuse-test) to the network using this call. I tried a couple of other but this is the only one that produced a join: osuse-test:/usr/local/samba/var # ../bin/net rpc join -v -S PDCHOST -Uroland No realm has been specified! Do you really want to join an Active Directory server? Enter roland's passw...

...ing 4.2.2 member server. Adding "require strong key = no" and "client NTLMv2 auth = no" to the member servers smb.conf but it did not change anything. Here is the log file on the dedicated member server of one client trying to connect my member server: SID for local machine OSUSE-TEST is: S-1-5-21-1853263269-3041869306-167322181 SID for domain MYDOM is: S-1-5-21-290147797-1639656955-1287535205 Join to 'MYDOM' is OK [2015/07/06 08:02:46.342573, 3] ../source3/smbd/oplock.c:1306(init_oplocks) init_oplocks: initializing messages. [2015/07/06 08:02:46.342706, 3] .....

...) Hence, submitting this upstream. Concern: When a private key (ex. key1) is used and there's a public key with the same file name+pub extension (ex. key1.pub) in the same directory, the automatic login will fail and will drop the user to the password prompt. Sample openssh version: santi at osuse:~> rpm -qi openssh Name : openssh Version : 7.2p2 Release : 6.1 Architecture: x86_64 Install Date: Wed 04 Jan 2017 10:01:31 AM PHT Group : Productivity/Networking/SSH Size : 5576705 License : BSD-2-Clause and MIT Signature : RSA/SHA256, Tue 18 Oct 2016 09:01:48...