Displaying 20 results from an estimated 3000 matches similar to: "Best practices for confidential information -- fileserver path vs modules / template"
2004 Aug 06
2
mountpoint
can anybody explain to me the mountpoint that is mentioned by icecast
version 1.3.12?
I see that the mountpoint is /default
what does this mean and how can I change it in the icecast.conf file.
I am running this on a freebsd 4.7 STABLE release.
- Noah
<p>--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from
2020 Mar 20
1
Listenurl is not in HTTPS
No, this is a relay of a Shoutcast server.
Everything is configured in https on IceCast ( https://relay2.dgnet.be/ ) , except this value listenurl ( in Admin / Mountpoint) which in cannot change apparently.
So the .m3u file is created with an http:// link ( instead of https:// )
But the stream is available and working in https://relay2.dgnet.be:443/different.ogg
Danny
From: Icecast
2014 Jun 07
2
icecast 2.4 check if source exists?
On 06/06/2014 01:08 PM, uno wrote:
> ... to answer myself:
>
> i had a fallback-mount specified, after removing it
> things work as expected. sorry for the noise.
In case of fallbacks you have to check properly through querying a
custom XSL, JSON or the admin backend.
> btw: what's the prefered way to get server and/or listener info?
2001 Mar 17
2
smbclient/mount question
This is driving me up the wall. I've had a basic samba server up for a
couple of years and it was easy to do. Now with a second server I try to
mount the same shares from the new linux box but I can get nothing to
work. I would use NFS between the linux boxes but the support isn't
compiled into my kernel, and I don't want to tackle that beast tonight...
To test I tried the smbclient
2004 Aug 06
2
'ice_login' not in icecast.xml ?
On Thu, 10 Oct 2002, Dave St John wrote:
> > username: source
> source meaning
> localhost
> or http://myip:myport/mymount
> Be specific please ;-)
ource as in "source".
Geoff.
<p><p>--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
2004 Aug 06
9
Stuttering stream
> Done, and it's working... but not significantly better than before.
> Whereas before I couldn't clear a single song without the stream devolving
> into skipping, now I'm averaging between 15-20 minutes. Better, but still
> not acceptable.
THen I suggest you start to look elsewhere for your problem. libshout
is quite well tested and every time someone has thought it was
2004 Aug 06
2
'ice_login' not in icecast.xml ?
Hi:
The authentication for the xml stats is as follows:
username: source
password: <the password you've put in the config file>
The icelogin item is to allow older style source logins (i.e. not the http
authentication that was implemented a number of weeks ago). this login is
deprecated, so it's been deliberately left out of the XML configuration
example.
Geoff.
<p>
--
2014 Jun 06
3
icecast 2.4 check if source exists?
hello,
i've upgraded to 2.4. in order to use url-auth etc.
works fine, but now i have a problem:
i've to check if a source exists. i did so by fetching
headers for a mountpoint, example
wget -S http://server:8000/test
if a mountpoint existed in icecast 2.3.2 (my previous version),
it returned something like "200 OK", when a source was connected.
now in 2.4. it always
2008 May 06
0
[LLVMdev] debugging LLVM generated executables???
Hi everyone again,
I did discover the following works (see below). However, does anyone
know of the "proper" way with LLVM?
llvm-gcc -g -c -emit-llvm helloworld.c
opt -load=mypass.dylib -mypass < helloworld.o > helloworld-mypass.o
llc -fast -f -o helloworld.s helloworld-mypass.o
as -o helloworld-prime.o
gcc -o helloworld helloworld-prime.o
gdb helloworld
On May 5, 2008, at
2012 Apr 03
1
Package seems to be present but library don't find it
Hi,
I try to make my first package? The HelloWorld.R file is:
#### HelloWorld.R ####
#' showHello est une fonction R permettant d'afficher le message
#' "Hello World!" sur la console.
#' @title la fonction showHello()
showHello <-function(){
cat("Hello World!\n")
}
I use the following procedure to get the tar:
# set the working directory where the file is
2008 May 06
0
[LLVMdev] debugging LLVM generated executables???
> I think you probably need to pass -O0 to llvm-ld. The link-time
> optimizations are probably killing your debug info.
>
No dice. Doing it this way makes gdb spew out this:
warning: Could not find object file "/var/folders/cQ/cQ+L3+RP2RWOpE
+8ZNQdPU+++TI/-Tmp-//ccVljWhn.o" - no debug information available for
"defs.h"
And then no debug symbols are available.
2008 May 06
2
[LLVMdev] debugging LLVM generated executables???
I think you probably need to pass -O0 to llvm-ld. The link-time
optimizations are probably killing your debug info.
--Owen
On May 5, 2008, at 8:21 PM, Mark Oskin wrote:
> Hi everyone again,
>
> I did discover the following works (see below). However, does anyone
> know of the "proper" way with LLVM?
>
> llvm-gcc -g -c -emit-llvm helloworld.c
> opt
2008 May 07
0
[LLVMdev] debugging LLVM generated executables???
On Wed, 7 May 2008, Mark Oskin wrote:
> Just re-sending this. Anyone have any suggestions on how to proceed
> with debugging LLVM produced executables? The problem appears to be
> register-allocated variables. Global variables and syntax lines do
> get symbols using the llc / as method I described below. -Mark
Have you considered adding your pass to llvm-backend.cpp in llvmgcc?
2008 May 07
1
[LLVMdev] debugging LLVM generated executables???
I could do that, but before I venture there, if I did that, could I
have llvm-gcc produce native object files (not LLVM bytecode) that way
(using my pass)? thanks, -Mark
On May 7, 2008, at 11:40 AM, Chris Lattner wrote:
> On Wed, 7 May 2008, Mark Oskin wrote:
>> Just re-sending this. Anyone have any suggestions on how to proceed
>> with debugging LLVM produced executables?
2008 May 07
2
[LLVMdev] debugging LLVM generated executables???
Just re-sending this. Anyone have any suggestions on how to proceed
with debugging LLVM produced executables? The problem appears to be
register-allocated variables. Global variables and syntax lines do
get symbols using the llc / as method I described below. -Mark
On May 6, 2008, at 7:36 AM, Mark Oskin wrote:
>
>> I think you probably need to pass -O0 to llvm-ld. The
2007 Nov 07
1
A more elegant way of obtaining the major OS release number
Hello all:
> We operate in an environment where we might sometimes wish to do
> certain tasks based solely upon the MAJOR version number of an OS
> release, disregarding the minor portion of the version number. For
> instance, CentOS 4.0 through 4.5 would all be ''CentOS 4'' to some
> scripts, and CentOS 5.0 and greater would all be ''CentOS 5''.
2011 Sep 29
1
[LLVMdev] Beginner Question on Linking
I am following along in http://llvm.org/docs/GettingStartedVS.html with a
Hello World bitcode file. I can run the file using the command `lli
HelloWorld.bc`, but now I want to link it into an executable file (on
windows). The next thing the document says to run is `llc -filetype=obj
HelloWorld.bc` which runs fine and now I have a `HelloWorld.obj` file. It's
the last step that is giving me some
2012 Nov 06
0
[LLVMdev] vmjc + llc questions
Hi,
I've been trying to compile a simple helloworld Java program to native
code, and I've been having trouble. I'm tripping an assertion that I don't
quite understand yet. I'm just curious if anybody can point me in the right
direction.
$ javac helloworld.java
$ vmjc -o helloworld.bc helloworld.class
$ llc -load=<...>/Release+Asserts/lib/StaticGCPrinter.so helloworld.bc
2006 Sep 12
2
Memory problems with a custom R package
Hi everyone,
I have been attempting to build a very simple R package interfacing with
some very simple C++ code. Everything I try though results in the
function working but on return it produces a memory error. Here is the
output:
***********OUTPUT***************************
> library(MyPackage)
> hello();
*** caught segfault ***
address 0x3, cause 'memory not mapped'
2008 May 05
2
[LLVMdev] debugging LLVM generated executables???
Hi everyone,
I have a question that seems simple, but has been confounding me for
several hours. I'd like to debug a binary produced with LLVM. For
the life of me, I can't get any symbols into gdb and llvm-db won't
even start the program nor load any useful information about it.
Here's my current strategy (which isn't working):
llvm-gcc -g -O0 -c -emit-llvm