search for: brl

...log, to see if you see anything strange? I'm putting a dump off the level 1 log, for you to check, i know it's more general, but if you notice anything, then i will increase it to see it better! [2012/01/04 11:07:44.992938, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 11:08:04.996512, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 11:08:41.711133, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean sh...

...t users don't have any noticable problems. ( Tried to find matching entries in the client logs - loglevel 2 ): -------------------------------------------------------------------------------- log.smbd: 2012/05/29 10:21:18.261416, 1] smbd/server.c:300(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/05/29 10:21:38.262575, 1] smbd/server.c:272(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown log.bhs013: [2012/05/29 10:21:18.251213, 2] smbd/process.c:2455(deadtime_fn) Closing idle connection [2012/05/29 10:21:18.25...

I've been interested in llvm for some time, and I finally got around to testing it with BRL-CAD. I first built llvm and clang from the current svn trunk, but that generated a crash report (llvm bug 16921 just submitted to llvm.org). Then I installed clang+llvm (v. 3.3.0) on Debian amd64 from pre-built binaries and got a good BRL-CAD build (but I haven't done the regression tests yet)...

...t;>> >> > I haven't been able to build gcc 4.7.3 yet (prereq ppl build problems--I > think that's why I stopped building gcc some time ago), but I did have > success with building gcc-4.8.1 (ppl no longer required). > > Sorry for a bit of a false alarm: I forgot a BRL-CAD release build has -Werror turned on, so I'm not yet sure if that affects clang or not with the way I configured the CMake build (I merely changed the paths to the C and C++ compilers) . That has uncovered a slew of errors not caught with gcc 4.4.5 or > I should have said: That has u...

On Fri, Aug 16, 2013 at 2:58 PM, Tom Browder <tom.browder at gmail.com> wrote: > On Fri, Aug 16, 2013 at 2:55 PM, Tom Browder <tom.browder at gmail.com>wrote: > >> ... >> > I'll see if I can try it with gcc 4.7 soon. >> > I haven't been able to build gcc 4.7.3 yet (prereq ppl build problems--I think that's why I stopped building gcc some time

...I did smbclient -L=server, and that shows all shares of the server. I sniffed with wireshark, but I see no traffic when a user tries to log in. What I see in /var/log/samba/smbd puzzles me (it's in Dutch) : [2012/03/23 16:34:06.760408, 1] smbd/server.c:240(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/03/23 16:40:28.222148, 1] smbd/server.c:267(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/03/23 16:40:48.224409, 1] smbd/server.c:240(cleanup_timeout_fn) Cleaning up brl and lock database after unclea...

...ba on a fully updated CentOS-6.3 box as a fileserver exporting to Win7 clients. samba-3.5.10-125.el6.x86_64 Anybody got an idea what is causing the following error message. It's filling up my logs. [2012/09/19 11:40:20.710031, 1] smbd/server.c:267(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/09/19 11:40:40.729746, 1] smbd/server.c:240(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown This is only seen on CentOS-6.3 a replacement server for CentOS-5.8 an not on another CentOS-5.8 box. It doesn't seem to a...

...8 17:25:21.980756, 3] printing/pcap.c:189(pcap_cache_reload) reload status: ok *[2012/08/28 17:37:08.715154, 3] smbd/server.c:292(remove_child_pid)* * smbd/server.c:292 Unclean shutdown of pid 32526* *[2012/08/28 17:37:08.715318, 1] smbd/server.c:300(remove_child_pid)* * Scheduled cleanup of brl and lock database after unclean shutdown* *[2012/08/28 17:37:28.722037, 1] smbd/server.c:272(cleanup_timeout_fn)* * Cleaning up brl and lock database after unclean shutdown* [2012/08/28 17:38:22.509303, 3] smbd/server.c:629(smbd_parent_housekeeping) Printcap cache time expired. [2012/08/28 17:...

...ht with gcc 4.4.5 or >> clang 3.3. >> > Attached is a list of the gcc-4.8.1 warnings from a trunk rev 56916 build (made into errors) that, for some reason, don't show in a debug build (looks like compile flags may be different but I'm not sure at the moment--need to dig into BRL-CAD CMake environment some more). They look like legit problems but I haven't tried to fix them. Best, -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130817/a19968ec/attachment.html>

...0 (IP ::ffff:X.X.X.X) Then I do a manual shutdown via kill -9: /var/log/samba/smbd.log: [2016/12/16 11:17:38.849553,  3] smbd/server.c:259(remove_child_pid)   smbd/server.c:259 Unclean shutdown of pid 14730 [2016/12/16 11:17:38.849606,  1] smbd/server.c:267(remove_child_pid)   Scheduled cleanup of brl and lock database after unclean shutdown [2016/12/16 11:17:58.869695,  1] smbd/server.c:240(cleanup_timeout_fn)   Cleaning up brl and lock database after unclean shutdown [2016/12/16 11:17:58.870256,  2] lib/messages_local.c:289(message_notify)   message to process 14730 failed - No such process [2...

...windows error: "Controller for the domain could not be found." This is at odds with the Samba log that shows the client does find the controller, but then stops talking. Thanks for the suggestion. Rejoining the domain does not help, and Samba still throws the "Scheduled cleanup brl and lock database after unclean shutdown" or "Cleaning up brl and lock database after unclean shutdown" messages. >>3.5.3 does not build a browse list of other domains >>on the subnet. Executing "net view /DOMAIN:mydomain" on the client >>produces an...

...6:17.136096, 0] lib/util_sock.c:1440(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. [2013/05/01 09:36:17.137700, 1] smbd/server.c:299(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2013/05/01 09:36:17.178522, 1] smbd/service.c:1073(make_connection_snum) 172.24.120.139 (172.24.120.139) connect to service Staff initially as user DOMAIN+admin (uid=10001423, gid=10000514) (pid 25771) [2013/05/01 09:36:17.179093, 0] lib/util_sock.c:47...

...l settings for gigabit ethernet - Tuned samba's settings based on various online discussions The problems still persist. Looking at last night's failure I found the following log messages: log.smbd [2010/08/25 00:37:15.551263, 1] smbd/server.c:267(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2010/08/25 00:37:35.551964, 1] smbd/server.c:240(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown Those are the only messages logged for last night, and line up exactly with the backup failures. The smbd process was last res...

...13.709782, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer. [2011/08/06 16:56:13.722554, 1] smbd/server.c:267(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown What is going wrong here? How can I fix this, so that the Windows 7 machine can correctly logon? Thanks for all the help! Kind regards, Raymond

...t;>the domain could not be found." This is at odds with the Samba log that >>shows the client does find the controller, but then stops talking. >> >>Thanks for the suggestion. Rejoining the domain does not help, and Samba >>still throws the "Scheduled cleanup brl and lock database after unclean >>shutdown" or "Cleaning up brl and lock database after unclean shutdown" >>messages. > >OK, this is going to sound a bit odd, but try this on the server: > >net rpc join <DOMAIN NAME> -U Administrator > >then, see...

...ain+0xf0) [0x7f8084797580] #34 /usr/sbin/smbd(_start+0x29) [0x559a31f80b79] [2016/01/04 11:02:44.204972, 0] ../source3/lib/dumpcore.c:318(dump_core) dumping core in /var/log/samba/cores/smbd [2016/01/04 11:02:46.031923, 1] ../source3/smbd/server.c:486(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2016/01/04 11:03:06.034312, 1] ../source3/smbd/server.c:429(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown --- The server and samba is up-to-date today, latest fedora 23 packages. The/one problematic share for him: [home...

On May 24, 2008, at 11:43 AM, Marcel Moolenaar wrote: > All, > > So far I've tried LLVM on amd64, i386, ia64 and powerpc under FreeBSD > and aside for ia64, things look pretty good for a first try. There > are 2 unexpected failures for PowerPC, which appear to be caused by > uninitialized memory. I'm still working on a fix for that (need to > brush up on my C++

...some protocols, including SSH. We don't know what exactly they've done but it appears to be some routing rule that prevents SSH protocol to initiate a connection. Its like that the handshake packet is dropped. Fortunately there is a patch on OpenSSH done by Bruce Leidl ( https://github.com/brl/obfuscated-openssh) that obfuscates the handshake packet and luckily it helps us pass through this annoying packet filtering. But sadly this patch isn't implemented in the main project. We, a group of Iranian OpenSSH users, recommend you to include this useful patch in the main project because...

All, So far I've tried LLVM on amd64, i386, ia64 and powerpc under FreeBSD and aside for ia64, things look pretty good for a first try. There are 2 unexpected failures for PowerPC, which appear to be caused by uninitialized memory. I'm still working on a fix for that (need to brush up on my C++ skills). [sidenote: In FreeBSD -current, the memory allocator initializes memory with 0xa5

...t;, while Windows 7 says "there are currently no logon servers available to service the logon request" I have looked at the smb/nmb/winbind logs at level 3 and near as I can tell everything is operating correctly although something seems to be crashing a lot--there are many entries about brl and lock database after unclean shutdown. I don't know SMB protocol very well but from watching some wireshark traces and reading the corresponding logs it looks like the nodes are negotiating IPC$ connection but not getting data. Client asks for copy 4, server offers copy 1, client negotiates...