search for: pefectly

Hello I have a problem on keeping the format when I export a matrix file with the write.table() function. When I import the data volcano from rgl package it looks like this in R: > data[1:5,] [,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8] [,9] [,10] [,11] [,12] [,13] [,14] [1,] 100 100 101 101 101 101 101 100 100 100 101 101 102 102 [2,] 101 101 102 102 102 102 102

Hello all. I currently have a method that is accessed from a form using this: View: <%= start_form_tag :action => :history %> <p><label for="componentlog_cl_compname">Component Name</label><br /> <%= text_field ''componentlog'', ''cl_compname'', :class => ''mandatory'', :value =>

What SoftPhone working very well with *? S.O. is Debian Linux Thanks for your comments. JRR _________________________________________________________________ MSN Amor: busca tu ? naranja http://latam.msn.com/amor/

...an LDAP backend. User logon restrictions, in terms of allowed logon hours are set by using NT's "User Manager.exe" which connects to the Samba controlled domain. The restrictions appear to work OK except when there are multiple rules for the logon hours. .e.g Logon restrictions work pefectly if the logon time is: 13:00-17:00, but not when there is more than one 'rule' e.g. 13:00-14:00 and 15:00-17:00. As soon as there is more than one rule users cannot log on and if I try to use smbclient I get something like and error like INVALID_LOGON_HOURS. Any ideas ? Your assistance is...

Hello, I'm facing a weird problem and I really do not know where I can find how to debug it. Since some years, we have a LDAP server ( Debian 6 and OpenLDAP 2.4.23 ) and a Samba server ( Debian 6 and Samba 3.5.6 ). They work pefectly well in a workgroup. The LDAP server is also used for some other applications like Squid, Zimbra, ... Now, we would to add a second Samba server ( Debian 7 and Samba 3.6.6 ). After having set up the server as I did for the other one, any login is allowed for LDAP users. On the console, getenv...

...and a 'Failed to verify incoming ticket' error in the logs. This behaviour occurs with accessing it via "\\hostname\"; when its accessed via "\\ip-address\", it works perfectly. Nothing has changed with the configuration and this is stumping me. Because 3.0.5 works pefectly with both hostname and ip-address, 3.0.6 / 7 does not. Any ideas ? I was hoping it was a glitch in the 3.0.6 package, but I don't want to stay behind too long as this is a public server. Thank you. -- ODC <odc-public@hotpop.com> Public E-Mail Drop *Hotpop is known to have unreliable...

Ya ya i know a little over the top.. I got the program to install and run surprisingly smooth actually, the only issue I have is when it comes time to install the games using the steam client. Under the my games section when i select a game and click install the program crashes. This is what I am getting in the log. ------------------- err:ole:CoGetClassObject class

...everal tries, I understood that the TLS negociation was not possible using TLSv1.2 (It works only with TLSv1.1) but my issue is I don't understand why : - The GNU TLS Library provided by CentOS is TLSv1.2 compliant. I can use gnutls-cli in order to make a TLSv1.2 connection - It also works pefectly with an openssl client, so it's not a server side issue. - I don't see anything in the lftp changelog or features list saying that lftp is not compliant with TLSv1.2. So my question is : Can lftp provided by CentOS (of course last version in the 6.x branch), do TLSv1.2 connection ?...

I get the following mysql error when I try to connect to my Linux machine using putty. Unknown database ''db_develoment'' (Mysql::Error) any idea what i need to do to avoid this. The same code works pefectly well on the Linux box. /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.2/lib/active_record/ven?dor/mysql.rb:508:i n `read'': Unknown database ''db_develoment'' (Mysql::Error) from /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.2/lib/active_record/ven?dor/m...

On 18/05/16 16:16, Markus Dellermann wrote: > Hi, > Am 18.05.2016 um 15:39 schrieb Robert K. Nelson: >> We are using samba4 as an AD controller under OpenSuSE 13.2 using the >> repository at: >> >> http://download.opensuse.org/repositories/network:/samba:/TESTING/openSUSE_13.2 >> >> > Not related to your Problem, but are you sure, that this repo really

...terms of allowed logon hours are set by using >> NT's "User Manager.exe" which connects to the Samba controlled domain. >> The restrictions appear to work OK except when there are multiple rules >> for the logon hours. >> .e.g >> Logon restrictions work pefectly if the logon time is: 13:00-17:00, but >> not when there is more than one 'rule' e.g. 13:00-14:00 and 15:00-17:00. >> As soon as there is more than one rule users cannot log on and if I try >> to use smbclient I get something like and error like INVALID_LOGON_HOURS. >...

On 05/19/2016 03:16 AM, Markus Dellermann wrote: > Am Mittwoch, 18. Mai 2016, 17:10:13 CEST schrieb Rowland penny: >> On 18/05/16 16:16, Markus Dellermann wrote: >> ... >>> Not related to your Problem, but are you sure, that this repo really >>> provide ad-dc - funktionality?? >>> >>> Markus >> It looks like you are right, there is also

...terms of allowed logon hours are set by using >> NT's "User Manager.exe" which connects to the Samba controlled domain. >> The restrictions appear to work OK except when there are multiple rules >> for the logon hours. >> .e.g >> Logon restrictions work pefectly if the logon time is: 13:00-17:00, but >> not when there is more than one 'rule' e.g. 13:00-14:00 and 15:00-17:00. >> As soon as there is more than one rule users cannot log on and if I try >> to use smbclient I get something like and error like INVALID_LOGON_HOURS. >...

...d that the TLS negociation was not possible > using TLSv1.2 (It works only with TLSv1.1) but my issue is I don't understand > why : > - The GNU TLS Library provided by CentOS is TLSv1.2 compliant. I can use > gnutls-cli in order to make a TLSv1.2 connection > - It also works pefectly with an openssl client, so it's not a server side > issue. > - I don't see anything in the lftp changelog or features list saying that lftp > is not compliant with TLSv1.2. > > So my question is : Can lftp provided by CentOS (of course last version in the > 6.x bra...

Am Mittwoch, 18. Mai 2016, 17:10:13 CEST schrieb Rowland penny: > On 18/05/16 16:16, Markus Dellermann wrote: > > Hi, > > > > Am 18.05.2016 um 15:39 schrieb Robert K. Nelson: > >> We are using samba4 as an AD controller under OpenSuSE 13.2 using the > >> repository at: > >> > >>

On 19/05/16 16:16, Robert K. Nelson wrote: > On 05/19/2016 03:16 AM, Markus Dellermann wrote: >> Am Mittwoch, 18. Mai 2016, 17:10:13 CEST schrieb Rowland penny: >>> On 18/05/16 16:16, Markus Dellermann wrote: >>> ... >>>> Not related to your Problem, but are you sure, that this repo really >>>> provide ad-dc - funktionality?? >>>>

Hi to all, I've tried to use the ASTCC credit check a long time ago and it worked pefectly, but now... no more Any suggestions for some new software? Thanks to all. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070410/22c5efcc/attachment.htm

...but winbind wouldnt work. So I went back down to 2.2.3a This was before Red Hat 8.0 came out. I gave up for the rest of that week since 8.0 came out the following week. Last week I had the spare time to wipe a spare machine and put 8.0 on, and enabled Samba 2.2.5 in the install. The shares work pefectly, but again winbind does not. I mimicked everything I did for the Samba 2.2.3 install I added the proper lines to nsswitch.conf passwd: files winbind group: files winbind My samba pam module has the following auth sufficient /lib/security/pam_winbind.so auth required /lib/security/pam_p...

...terms of allowed logon hours are set by using >> NT's "User Manager.exe" which connects to the Samba controlled domain. >> The restrictions appear to work OK except when there are multiple rules >> for the logon hours. >> .e.g >> Logon restrictions work pefectly if the logon time is: 13:00-17:00, but >> not when there is more than one 'rule' e.g. 13:00-14:00 and 15:00-17:00. >> As soon as there is more than one rule users cannot log on and if I try >> to use smbclient I get something like and error like INVALID_LOGON_HOURS. >...

On 05/19/2016 11:57 AM, Rowland penny wrote: > On 19/05/16 16:16, Robert K. Nelson wrote: >> On 05/19/2016 03:16 AM, Markus Dellermann wrote: >>> Am Mittwoch, 18. Mai 2016, 17:10:13 CEST schrieb Rowland penny: >>>> On 18/05/16 16:16, Markus Dellermann wrote: >>>> ... >>>>> Not related to your Problem, but are you sure, that this repo really