search for: start_daemon

...rver (f_in=3, f_out=3, argc=<value optimized out>, argv=<value optimized out>) at main.c:1104 #10 0x000000000043c5b8 in rsync_module (f_in=3, f_out=3, i=3, addr=<value optimized out>, host=0x67d2a0 "tjtx-100-201.58os.org") at clientserver.c:1003 #11 0x000000000043d58d in start_daemon (f_in=3, f_out=3) at clientserver.c:1094 #12 0x0000000000433b20 in start_accept_loop (port=873, fn=0x43d3b0 <start_daemon>) at socket.c:618 #13 0x000000000043d77b in daemon_main () at clientserver.c:1196 #14 0x000000000041ee25 in main (argc=0, argv=0x0) at main.c:1621 (gdb) -- You are recei...

.../rc.d/init.d/dovecot start (code=exited, status=127) Mar 18 16:32:17 systemd[1]: Starting LSB: Starts the Dovecot POP3/IMAP service... Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 34: log_info_msg: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 35: start_daemon: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 36: evaluate_retval: command not found Mar 18 16:32:17 systemd[1]: dovecot.service: control process exited, code=exited status=127 Mar 18 16:32:17 systemd[1]: Failed to start LSB: Starts the Dovecot POP3/IMAP service....

...st are apropos as well; at least one person was asking if there is any way to get modules with ssh. GORY DETAILS: The code changes are about 150 lines, plus 70 lines of man page changes. Most of the code changes were to several functions (e.g. auth_server(), start_accept_loop(), rsync_module(), start_daemon()) to make them handle two file descriptors (f_in and f_out) instead of one bidirectional socket file descriptor (fd). Other changes include: - main() will call start_daemon() instead of start_server() if the program is called with both '--server' and '--daemon'. - start_da...

...08 #6 0x415bee in recv_file_list /home/raj/rsync/rsync/flist.c:2476 #7 0x454eaa in do_server_recv /home/raj/rsync/rsync/main.c:1036 #8 0x4556f4 in start_server /home/raj/rsync/rsync/main.c:1115 #9 0x4b20f2 in rsync_module /home/raj/rsync/rsync/clientserver.c:1007 #10 0x4b2b11 in start_daemon /home/raj/rsync/rsync/clientserver.c:1135 #11 0x48f636 in start_accept_loop /home/raj/rsync/rsync/socket.c:618 #12 0x4b32d2 in daemon_main /home/raj/rsync/rsync/clientserver.c:1237 #13 0x458318 in main /home/raj/rsync/rsync/main.c:1630 #14 0x7ffff64d866f in __libc_start_main (/lib64...

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

...14) at util.c:548 548 if (!(argv[argc++] = strdup(globbuf.gl_pathv[i]))) (gdb) where #0 0x08056577 in glob_expand (base1=0x5 <Address 0x5 out of bounds>, argv_ptr=0xbfa4a20c, argc_ptr=0xbfa4a210, maxargs_ptr=0xbfa4a214) at util.c:548 #1 0x080710f6 in start_daemon (f_in=7, f_out=7) at clientserver.c:451 line 451: glob_expand(name, &argv, &argc, &maxargs); line 232: char *name = lp_name(i); within gdb: print lp_name $1 = {char *(int)} 0x806f0c0 <lp_name> (gdb) print lp_name@5 $2 = {{char *(int)} 0, {char *(int)} 0, {char *(int)...

.../lib/x86_64-linux-gnu/libc.so.6 #14 0x00007fa75efc5666 in gethostbyaddr_r () from /lib/x86_64-linux-gnu/libc.so.6 #15 0x00007fa75efcae1d in getnameinfo () from /lib/x86_64-linux-gnu/libc.so.6 #16 0x0000000000441002 in lookup_name () #17 0x0000000000440e3b in client_name () #18 0x000000000044d566 in start_daemon () #19 0x000000000043eb74 in start_accept_loop () #20 0x000000000044da7e in daemon_main () #21 0x0000000000425751 in main () strace output which shows segmentation fault. 7241 read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3008\0\0\0\0\0\0"..., 832) = 832 7241 fstat(5, {st_...

...libc.so.1 #2 0x00025ee8 in writefd_unbuffered () #3 0x00026f4c in io_multiplex_write () #4 0x0001ce6c in rwrite () #5 0x0001cfcc in rprintf () #6 0x00012ae0 in recv_generator () #7 0x000139fc in generate_files () #8 0x00019528 in do_recv () #9 0x000197f4 in start_server () #10 0x0002fec4 in start_daemon () #11 0x00030088 in daemon_main () #12 0x0001a52c in main () server child process: #0 0xff19db44 in _poll () from /usr/lib/libc.so.1 #1 0xff15236c in _select () from /usr/lib/libc.so.1 #2 0x000251e0 in read_timeout () #3 0x00025cc4 in readfd_unbuffered () #4 0x0002651c in read_buf () #5 0...

Hi, When I have my rsync daemon running, I get all log messages in a custom format in the file /var/log/rsyncd.log. This is very convenient as I can cron a script to grep it and mail me a summary of activity every day and then create a fresh file. I have now switched to using rsync over ssh, so I stopped the rsync daemon, and every user has an authorised ssh key and a *custom* rsyncd.conf (with

Hi experts, First I post my log root@intel_5500_server:/> ifconfig eth0 Link encap:Ethernet HWaddr 00:15:17:BB:5E:88 inet addr:128.224.165.205 Bcast:128.224.165.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:febb:5e88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2375 errors:0 dropped:0 overruns:0 frame:0

...util.c:1077 #1 0x449484 in glob_expand /home/raj/rsync/rsync/util.c:717 #2 0x449af8 in glob_expand_module /home/raj/rsync/rsync/util.c:783 #3 0x478b61 in read_args /home/raj/rsync/rsync/io.c:1266 #4 0x4b12b6 in rsync_module /home/raj/rsync/rsync/clientserver.c:869 #5 0x4b2a49 in start_daemon /home/raj/rsync/rsync/clientserver.c:1135 #6 0x48f56e in start_accept_loop /home/raj/rsync/rsync/socket.c:618 #7 0x4b320a in daemon_main /home/raj/rsync/rsync/clientserver.c:1237 #8 0x4582da in main /home/raj/rsync/rsync/main.c:1627 #9 0x7ffff64d866f in __libc_start_main (/lib64/lib...

...in gethostbyaddr_r () from >> /lib/x86_64-linux-gnu/libc.so.6 >> #15 0x00007fa75efcae1d in getnameinfo () from >> /lib/x86_64-linux-gnu/libc.so.6 >> #16 0x0000000000441002 in lookup_name () >> #17 0x0000000000440e3b in client_name () >> #18 0x000000000044d566 in start_daemon () >> #19 0x000000000043eb74 in start_accept_loop () >> #20 0x000000000044da7e in daemon_main () >> #21 0x0000000000425751 in main () >> >> strace output which shows segmentation fault. >> 7241 read(5, >"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\...

...108 #3 0x415bee in recv_file_list /home/raj/rsync/rsync/flist.c:2476 #4 0x454eaa in do_server_recv /home/raj/rsync/rsync/main.c:1036 #5 0x4556f4 in start_server /home/raj/rsync/rsync/main.c:1115 #6 0x4b20f9 in rsync_module /home/raj/rsync/rsync/clientserver.c:1007 #7 0x4b2b18 in start_daemon /home/raj/rsync/rsync/clientserver.c:1135 #8 0x48f636 in start_accept_loop /home/raj/rsync/rsync/socket.c:618 #9 0x4b32d9 in daemon_main /home/raj/rsync/rsync/clientserver.c:1237 #10 0x458318 in main /home/raj/rsync/rsync/main.c:1630 #11 0x7ffff64d866f in __libc_start_main (/lib64/l...

...gc=2, argv=0x7f9a7302f240) at main.c:1107 #9 0x00007f9a71e5a34e in rsync_module (f_in=3, f_out=3, i=0, addr=0x7f9a72098518 <numeric_ids> "\377\377\377\377", host=0x7f9a72098c80 <name_buf> "host-a.example.com") at clientserver.c:1009 #10 0x00007f9a71e5b260 in start_daemon (f_in=3, f_out=3) at clientserver.c:1100 #11 0x00007f9a71e4f5d1 in start_accept_loop (port=4, fn=0x7ffe7c1aa160, fn at entry=0x7f9a71e5b120 <start_daemon>) at socket.c:618 #12 0x00007f9a71e5bb46 in daemon_main () at clientserver.c:1202 #13 0x00007f9a71e1aeb1 in main (argc=0, argv=0x0) at m...

...`ps -ef` if there are other `upssched` processes present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping `upssched`... If anyone decides to track through the code, the potential processing loop goes checkconf -> conf_arg -> parse_at -> sendcmd -> daemon if needed -> start_daemon -> conn_add(pipefd) or sock_read(conn) with short-lived child processes (command-line launched from `upsmon`) parsing the configuration to pick the part relevant to them per envvars, and talk to the daemon (fork one if needed) to start/cancel the timers. Jim On Tue, Jun 13, 2023 at 8:33?AM Kar...

...`ps -ef` if there are other `upssched` processes present, or look in `/proc/PIDNUM/fd/` of the daemonized and looping `upssched`... If anyone decides to track through the code, the potential processing loop goes checkconf -> conf_arg -> parse_at -> sendcmd -> daemon if needed -> start_daemon -> conn_add(pipefd) or sock_read(conn) with short-lived child processes (command-line launched from `upsmon`) parsing the configuration to pick the part relevant to them per envvars, and talk to the daemon (fork one if needed) to start/cancel the timers. Jim On Tue, Jun 13, 2023 at 8:33?AM Kar...

.../rc.d/init.d/dovecot start (code=exited, status=127) Mar 18 16:32:17 systemd[1]: Starting LSB: Starts the Dovecot POP3/IMAP service... Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 34: log_info_msg: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 35: start_daemon: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 36: evaluate_retval: command not found Mar 18 16:32:17 systemd[1]: dovecot.service: control process exited, code=exited status=127 Mar 18 16:32:17 systemd[1]: Failed to start LSB: Starts the Dovecot POP3/IMAP service....

...s 0x000000000000 (pc 0x000000453662 bp 0x7fffffffae90 sp 0x7fffffffae50 T0) #0 0x453661 in do_server_sender /home/raj/rsync/rsync/main.c:786 #1 0x4556a0 in start_server /home/j/rsync/rsync/main.c:1110 #2 0x4b202a in rsync_module /home/j/rsync/rsync/clientserver.c:1007 #3 0x4b2a49 in start_daemon /home/j/rsync/rsync/clientserver.c:1135 #4 0x48f56e in start_accept_loop /home/j/rsync/rsync/socket.c:618 #5 0x4b320a in daemon_main /home/j/rsync/rsync/clientserver.c:1237 #6 0x4582da in main /home/j/rsync/rsync/main.c:1627 #7 0x7ffff64d866f in __libc_start_main (/lib64/libc.so.6+0...

...ires changes to support "debian way" for xen-<version> within /usr/lib and /usr/share, but got into problems with some other lines in the patches (mainly tools-misc-prefix.diff where debian patches replaced execvp with execute from xen.util.auxbin and on xen 3.3.0 they implemented a start_daemon function, among some PATH problems). Since xen-unstable (the version from sid) didn't worked flawlessly on my setup (where 3.2-1 works) I'm willing to try to use the 3.2-1 packages as reference instead of xen-unstable, unless someone advises me the opposite or if such effort in already ong...

...in strlen () from /lib/i686/libc.so.6 (gdb) backtrace #0 0xb7ed78d3 in strlen () from /lib/i686/libc.so.6 #1 0x0807ff8d in strlcpy (d=0xbfed3434 "", s=0x0, bufsize=1024) at lib/compat.c:109 #2 0x0807bbc3 in lp_load (pszFname=0x0, globals_only=0) at loadparm.c:838 #3 0x0807cd53 in start_daemon (f_in=0, f_out=1) at clientserver.c:882 #4 0x0806348c in main (argc=1, argv=Cannot access memory at address 0x4 ) at main.c:1530 when i comment out this line (loadparm.c:838), there is no segmentation fault any more. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ----...