similar to: Locking Problems with Tracker 97

We have encountered a locking problem with multi-user Tracker 97 against Tracker data files on a Samba server. I do not believe it is related to erroneous smb.conf settings. If two separate users attempt to edit the same record, Tracker refuses the second request if a Win95 server or NT server is used, but allows the second request if a Samba server is used. Subsequently, the data files under

Try to ping from client to server with its hostname. Sounds like dns problem. ping server Then try to ping its ip address. Then try to add server address to host file. Ex 192.168.8.30 server.example.com[1] server Best M On May 26, 2016 12:02, "Nico Speelman" <nico at speelmanrobben.nl[2]> wrote: Hello, I've been trying to add a new server to my Samba 4 Active directory, but

Hi, this is the error message I do receive: Tracker-Message: 14:15:22.884: Could not get mtime for 'file:///nonexistent/.cache/tracker/meta.db': Error when getting information for file “/nonexistent/.cache/tracker/meta.db”: No such file or directory (process:5229): Tracker-WARNING **: 14:15:22.884: Falling back to bus backend, the direct backend failed to initialize: Could not open

I’m having this exact same issue after upgrading from 4.7.x to 4.9.1. I’ve been using the same set of instructions to setup tracker for a few years without issue. Does anyone have any suggestions? I’m stuck on this and can’t figure out what’s changed. Thanks. Mike Pestorich > Date: Mon May 14 12:31:28 UTC 2018 > From: Dirk Köppen > > Hi, > > this is the error message I do

Everyone, I think we have most of the kinks worked out of the new Alioth tracker notification mailing list: http://lists.alioth.debian.org/mailman/listinfo/nut-tracker List membership is open to all. For tracker items that you have submitted yourself, nothing has changed - you will still receive email updates when someone comments on your bug/feature/patch (or otherwise changes the tracker

Friends, At this point, we're close to 300 issues open in the bug tracker at http://bugs.digium.com Some of us spend many hours each week, if not each day, to work with the bug tracker. It's a tool for us, a very important tool to handle new features and find bugs in Asterisk, tracking them down. It is important that you consider a few things while using this tool: - If a bug marshal

I''m trying to download a torrent from a site that requires authentication, but the tracker refuses the connection. This is the error in the log: (With a slightly obfuscated passkey) -------------- trying tracker http://www.moviehouse.nl/announce.php?passkey=a60240a26d4018****************** warning: couldn''t connect to tracker, next try in 10 seconds connecting to

This is a cross-list post. I''d like to announce the initial release of a puppet request-tracker module, darin-rt, for managing Request Tracker. The module will install request-tracker and database packages, install request-tracker extensions (if packages are available in the repo), and create basic request-tracker queues. This is also a request for help in extending the module to

Dear Asterisk community, We are now working hard to complete Asterisk 1.2, testing and finalizing the existing patches and work that is going on in the developer team. Now is too late to file feature requests for 1.2 in the bug tracker. Unless you have a solid, working and tested patch, we will not consider the feature request on behalf of the developer team. A bug marshal will propably close

I have been hunting around the inet trying to find a CLI BT tracker/hoster. I want to use one of my linux servers as a BT torrent hoster/tracker. Anyone have any good informaiton they can point me to? -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the

During the last week, we have had several support issues being reported as bugs on the bug tracker. Since we are going into a final development stage on version 1.1dev (CVS HEAD) in order to complete the 1.2 release we are under pressure to fix bugs and handle a lot of reports in a short time frame. Neither the bug tracker or the asterisk-dev mailing list is second-line support, they're

Hi, Is there someone who could give me an advice about the correct usage of the tracker-wrapper ? As far as I understand the dbus service files must look like this: [Service] Type=simple GuessMainPID=no Environment="TRACKER_BUS_TYPE=system" ExecStart=/usr/lib/tracker/tracker-wrapper tracker-extract Restart=on-abort User=mdssvc Would this be the correct syntax?

Hello, I am working on a small booklet to be used with an existing statistics textbook. The purpose of the booklet is to give worked through examples from the textbook using R code and it will be made publicly available with the textbook. The title of the booklet is "R Code Supplement for Basic Engineering Data Collection and Analysis by Vardeman and Jobe". Someone with whom I'm

Asterisk buddies! If you have open issues in the bug tracker, please help us with providing fast responses. All developers are working real hard to close bugs pending the new release, so we kindly ask you for fast responses on our questions in the bug tracker. The quicker the better and we'll get 1.2 out of the door sooner. If you have new ideas, feature requests, thoughts - please keep the

As part of the ongoing move of FLAC's project hosting from sourceforge.net to xiph.org, we're planning to remove the issue tracker there. Erik doesn't check it, so issues filed there are just rotting, and that's a poor experience. We don't have a decent alternative at xiph.org at the moment. We've variously discussed setting up a bugzilla instance or using github. In the

Hello I am attempting to run a live feed from icecast, it was working an now isn't I have tried everything I can thing of, I am looking for some help to get back up and in service, I am at the point now that I will pay someone to get me up and running again. If anyone can help me contact me via email and i will explain what is going on Any help will be apprecated Thanks,

Hi Everyone, Just a friendly reminder that if you hit something you think is a bug, please use the bug tracker for it. http://rubyforge.org/tracker/index.php?group_id=1306&atid=5145 I have a hard time wading through the Forums, mailing list, and my personal e-mail box pulling out the bugs I need to fix. I just finished doing it for this last round and there was about 7 bugs and 5 feature

In an effort to ensure that every licensing issue brought to our attention is handled fully and openly, we have created a new issue tracker for this purpose. It is located at: http://licensing.digium.com The tracker is open to the public, and we encourage all interested parties to post their concerns and participate in the discussions involved in resolving them. Digium's will actively

In an effort to ensure that every licensing issue brought to our attention is handled fully and openly, we have created a new issue tracker for this purpose. It is located at: http://licensing.digium.com The tracker is open to the public, and we encourage all interested parties to post their concerns and participate in the discussions involved in resolving them. Digium's will actively

Ralph Giles wrote: > As part of the ongoing move of FLAC's project hosting from > sourceforge.net to xiph.org, we're planning to remove the issue tracker > there. Erik doesn't check it, so issues filed there are just rotting, > and that's a poor experience. > > We don't have a decent alternative at xiph.org at the moment. We've > variously discussed