similar to: 1rst startup of samba

Hi everybody, I am currently working on mixtures of two densities ( f(xi,teta)= (1-teta)*f1(xi) + teta*f2(xi) ), particularly on the behavior of the variance for teta=0 (so sample only comes from the first distribution). To determine the maximum likelihood estimator I use the Newton-Rapdon Iteration. But when computing the first derivative I get a none linear function (with several asymptotes)

Hi there, I have the lucky task to setup a Xen system. my plateform is a dell 2950 with 16Gb of RAM. I got as far as setting up debian sarge and xen following http://www.debian-administration.org/articles/423 and overcoming some specific difficulties (http://kmuto.jp/b.cgi/debian/d-i-2615.htm & http://wiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround) But, my concern now, while

i just got confused in creating machine accounts in my samba server 1rst creating the user [root@genesis root]# smbpasswd -a cpu3 New SMB password: Retype new SMB password: Added user cpu3. than adding the machine... [root@genesis root]# smbpasswd -a -m cpu3$ Failed initialise SAM_ACCOUNT for user cpu3$. Failed to modify password entry for user cpu3$ [root@genesis root]# what am i missing...

Additional information: I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. So memtest 4.1 and 4.2 worked with pxelinux 4.06 Peter > Date: Fri, 28 Jun 2013 09:02:30 +0100 > From: matt at console-pimps.org > To: coolpet80 at hotmail.com > CC:

Hi Leslie, 2014-09-29 17:14 GMT+02:00 Leslie Rhorer <lrhorer at mygrande.net>: > > I just did a fresh installation of Debian Jessie on one of my > servers, but NUT won't configure and install. When I try to install, I get > the following: > > Setting up nut-client (2.7.2-1+b2) ... > Job for nut-monitor.service failed. See 'systemctl status >

I just did a fresh installation of Debian Jessie on one of my servers, but NUT won't configure and install. When I try to install, I get the following: Setting up nut-client (2.7.2-1+b2) ... Job for nut-monitor.service failed. See 'systemctl status nut-monitor.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nut-client, action "start" failed.

Hi, I am working on a patch for FENTON.H to support some more ups models, I wonder if someone can help with further information,meaning and importance for the following values that are beeing set in the model capability table: float lowvolt; float voltrange; float chrglow; float chrgrange; int lowxfer; int lownorm; int highnorm; int highxfer; Thanks, Nadav

> Additional information: > I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. > So memtest 4.1 and 4.2 worked with pxelinux 4.06 > Peter > Yes, memtest boots from all variants of Syslinux 4.06. But, in Syslinux 4.06, there is linux.c32,

Hi all , my ices0.2.3/icecast1.3.12 has a sudden strange behaviour. For 3-4 months they ran without any ( yes , any ) problems. My box is a slackware linux one, on an ADSL line in France . I even was so satisfied of them that a let them runinng as deamon. ... But these past three days , ices seems to kill itself ....with that reason: (Ices and icecast are on the same box . That 1rst line appears

Hello guys, I was some years ago when I sent something to this list. NUT is a great tool but lacks SNMP management. It can access a device using SNMP but I found no way to read NUT values using SNMP. It would be very useful in order to integrate with network management software based on SNMP. As I did not find a solution, I wrote it myself. I wrote a MIB file and a SNMP agent for net-snmp

Hello guys, I was some years ago when I sent something to this list. NUT is a great tool but lacks SNMP management. It can access a device using SNMP but I found no way to read NUT values using SNMP. It would be very useful in order to integrate with network management software based on SNMP. As I did not find a solution, I wrote it myself. I wrote a MIB file and a SNMP agent for net-snmp

Hi David, it seems that your below mail went unmoderated :-/ anyway, any news on the appData side? as usual, I can provide help if needed... have you also been able to take a look at the pyNut3 thread / pull requests? cheers, Arno From: David Goncalves <david at lestat.st> To: Charles Lepple <clepple at gmail.com> Cc: <nut-upsdev at lists.alioth.debian.org> Date: Fri, 30 May

Hi all, I am very new to traffic control. I read the lartc how to and I am curently using the script in ch15 (cookbook) with some restricion : I excluded the ingress section and i implemented the rest on both interfaces of my firewall.(eth0 the internet interface and eth1 the LAN interface).find below the script use on eth1 (ssh priority one and all other 2)

Arnaud, you changed the "if" part, perhaps you'd like to change the "else" part, too? Changing the output format of HIDDumpTree() has the potential to break the functionality of scripts/subdriver/path-to-subdriver.sh; I don't think it does in this instance, but I have not checked it. Perhaps it would be good to add a comment in the source code as a caution. -- Peter

Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file

Hi David and fellows, I'm reviving this important thread about a common power management. To sum up, the first aim is to allow a better user experience on Linux by bridging NUT with Linux HAL, and Gnome Power Management / any PM GUI. But it also initiate a bigger investigation about how to integrate NUT support for UPSs into the native OS Power Management infrastructure for all supported

My keys are secured with a passphrase. That's good for security, but having to type the passphrase either at every login or at every invocation of ssh(1) is annoying. I know I could invoke ssh-add(1) just before invoking ssh(1), if I keep track of whether I invoked it already, or write some hacky scripts; but the rest of OpenSSH is wonderfully usable without any hacks. Hence, this patch.