search for: rroot

.../rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [tlf] path = / comment = export uid = root gid = root read only = yes hosts allow = 192.168.0.12 list = yes auth users = rsroot secrets file = /etc/rsyncd.secrets and /etc/rsyncd.secrets contains rroot:rroot On the computer where the data should be downloaded to do I use: rsync -avWHRx 192.168.0.6::tlf /media/backup/latest-tlf/ After entering the rroot password I get this error: @ERROR: auth failed on module tlf rsync error: error starting client-server protocol (code 5) at main.c(1296) [receiv...

...ded the dkim-milter-1.2.0 and uncompress it edited the site.config.m4 file n folled intructions in the INSTALL file but when i run sh Build it gives me errors here below a part of the errors tmp/software/dkim-milter-1.2.0/libdkim Configuration: pfx=, os=Linux, rel=2.6.18-8.el5xen, rbase=2, rroot=2.6.18-8, arch=i686, sfx=, variant=optimized Making in /tmp/software/dkim-milter-1.2.0/obj.Linux.2.6.18-8.el5xen.i686/libdkim make[1]: Entering directory `/tmp/software/dkim-milter-1.2.0/obj.Linux.2.6.18-8.el5xen.i686/libdkim' make[1]: Nothing to be done for `all'. make[1]: Leaving di...

...ed that I may be messing up something. I tracked down the error by installing from the command line, rather than with install.packages(). On Windows I keep multiple versions of Rtools (and R) and start a command window with a batch file which has something like the following at its start: set Rroot=c:\ProgramF\R\R-3.3.2patched set RtoolsRoot=c:\PROGRAMF\R\Rtools3p3 To change the R version I simply copy the file and change the above two lines correspondingly. This worked for years until recently when > R CMD INSTALL Countr_3.2.8.tar.gz Produced an error: .... c:/Rtools/mingw_32/bin/g++:...

...e terminating CR of Q1 replies, > should work with your device. > > > root at artu:~# upsc Elit at artu > > Init SSL without certificate database > > Error: Driver not connected > > aehm, was the blazer_usb driver running? > ?This was tested with ? ?nutdrv_qx.... rroot at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Can't chdir to /var/run/nut: No such file or directory Driver failed to start (exit status=1) ?but with blazer_usb seems better.... ?root at artu:~# upsdr...

...#39;, it's working correctly. When you run the driver normally (i.e. not in debug mode), you don't see all that output (plus, after having established a connection with the device, the driver goes into the background), but it's doing exactly the same thing. > nutdrv_qx.... > > rroot at artu:~# upsdrvctl start > Network UPS Tools - UPS driver controller 2.7.2 > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) > Can't chdir to /var/run/nut: No such file or directory > Driver failed to start (exit status=1) > > but with blazer_usb seems better...

.................................................................................................................. = 0 lstat64("/dev/mem", 0x7f7f3220) ...................................................................................................................... = 0 lstat64("/dev/rroot", 0x7f7f3220) .................................................................................................................... = 0 lstat64("/dev/root", 0x7f7f3220) .......................................................................................................................

Hello, I've just installed the Samba 3.0.23a on a Solaris 10 box, 64-bit compiled. I'm running in to some problems though. When I try to change the password of a use this is the output I get: rroot@dune-sb0:/ >/usr/local/samba/bin/smbpasswd linus New SMB password: Retype new SMB password: init_account_policy: Failed to grant privileges to BUILTIN\Administrators! unknown fmt N ldapsam_modify_entry: LDAP Password could not be changed for user linus: Protocol error empty request da...

...When you run the driver normally (i.e. not in debug mode), you don't > see all that output (plus, after having established a connection with > the device, the driver goes into the background), but it's doing > exactly the same thing. > > > nutdrv_qx.... > > > > rroot at artu:~# upsdrvctl start > > Network UPS Tools - UPS driver controller 2.7.2 > > Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) > > Can't chdir to /var/run/nut: No such file or directory > > Driver failed to start (exit status=1) > > > > bu...

Use the name from ups.conf in front of "@localhost". ?The re?sult is quite different ;) root at artu:~# upsc Elit at artu Init SSL without certificate database Error: Driver not connected > What if you try nutdrv_qx without specifying megatec? (It should > autodetect.) > ?Here is the result: ? root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller