similar to: Bug Tracker Official Launch

All, As a bug marshal, I have noticed quite a few bugs that seem to get overlooked/ignored due to the fact that they do not have the appropriate information in the bug information fields, or bugnotes. I am, therefore, Reposting an old post from July 26th, 2003, to help clarify the use of the Bugtracker. Sorry if you have read it before; this is just an attempt to re-familiarize

Any ideas? Thanks. [root@localhost root]# asterisk -r Unable to connect to remote asterisk [root@localhost root]# asterisk -vvvvvgcd Parsing /etc/asterisk/asterisk.conf Asterisk 0.7.0, Copyright (C) 1999-2001 Linux Support Services, Inc. Written by Mark Spencer <markster@linux-support.net> ========================================================================= Parsing

Just curious if any of the Asterisk installers are doing anything special to protect themselves from a possible lawsuit caused by 911 failure during a Asterisk/computer crash? I realize that any traditional PBX or even a phone line can fail but, anything running on a computer is probably going to be less reliable than most PBXs. Anybody requiring customers to acknowledge and sign any kind of

On my registration form I have a checkbox for a waiver. In the model I have the statement: validates_acceptance_of :waiver, :on => :create, :message => "must be accepted" In the view: <%= check_box_tag("waiver") %> <%= error_message_on "user", "waiver", "Waiver "%> For some reason validate is accepting everything when the

This should have gone here and not to #706233. Patch will obviously need rebasing by now... ----- Forwarded message from Ian Campbell <ijc at hellion.org.uk> ----- Date: Fri, 16 Aug 2013 14:56:49 +0100 From: Ian Campbell <ijc at hellion.org.uk> To: 706233 at bugs.debian.org Cc: control at bugs.debian.org Subject: move core dumps to /var/lib/xen/dump X-Spam-Status: No, score=-4.9

tags 706233 +patch thanks This is somewhat more FHS compliant IMHO. commit 7d171826bc97bf5f3f2019fc32c1ca85b49de7c9 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 14:54:42 2013 +0100 * debian/patches/tools-core-dump-dir.patch: Switch tools to dumping to /var/log/xen/dump by default. * debian/xen-utils-common.dirs: Ensure /var/lib/xen/dump is created *

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

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

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

Hi All, I have corefile where we see NULL pointer de-reference PANIC as we have sent (deliberately) NULL pointer for return value. vdev_disk_io_start() ... ... error = ldi_ioctl(dvd->vd_lh, zio->io_cmd, (uintptr_t)&zio->io_dk_callback, FKIOCTL, kcred, NULL); ldi_ioctl() expects last parameter as an

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

Hi, All I test with ctdb-1.2.0-18.1, and there is a corefile. I want to analyze the corefile, but can't find the ctdb debuginfo. Could you tell me where to find the ctdb debuginfo? -- Best Regards. Yu Liao

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

Hi, I build llvm+clang+lldb 3.7 successfully on centos7, and lldb -p PID works pretty well. However when I tried lldb -c corefile executable_bin, lldb itself core dumpped. Attached the following core info which is debugged by gdb: [root at dn-cn-controller-4fbd4 data1]# lldb -c a.corefile /usr/local/myproject/bin/cnode *(lldb) target create "/usr/local/myproject/bin/cnode" --core

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

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?