Displaying 8 results from an estimated 8 matches for "belligerence".
2008 Oct 15
1
Error on man page
Hi
I discovered a similar problem early this week and a colleage on irc was
told it was a copy and paste error.
in man syslogd, the following can be found:
Sucker rod def. -- 3/4, 7/8 or 1in. hardened steel rod,
male threaded on each end. Primary use in the oil industry in Western
North Dakota and other locations to pump 'suck' oil from oil wells.
Sec-
ondary
2017 Oct 10
5
Flame war police
...un descended into some quite nasty places and
perhaps a lid should have been put on it. This seems to happen every few
weeks and is somewhat embarrassing when I'm trying to persuade people of
the "active and friendly Centos community"
It was a shame that no one actually read past the belligerence his original
post enough to come up with a solution. It was quite clearly a problem with
third party packages not coming with SELinux policies.
Cheers,
Andrew
2017 Oct 10
0
Flame war police
...uite nasty places and
> perhaps a lid should have been put on it. This seems to happen every few
> weeks and is somewhat embarrassing when I'm trying to persuade people of
> the "active and friendly Centos community"
>
> It was a shame that no one actually read past the belligerence his original
> post enough to come up with a solution. It was quite clearly a problem with
> third party packages not coming with SELinux policies.
Also just as clearly, everyone on the list said this wasn't standard
CentOS practice, the third party repo/packages OP used was not built
p...
2003 Dec 22
1
tor2 does not load
Hi list,
I have a asterisk box with an E400P that was running ok until last
week.
The machine just stop responding and after a reboot, the module (tor2)
doesn't load anymore.
anyone could help?
regards
Eduardo
modprobe returns this:
asterix:~# modprobe tor2
Zapata Telephony Interface Registered on major 196
Detected Tormenta 2 Quad T1/PRI or E1/PRA at 0xfe121800/0xfe121000 irq 7
2019 Sep 10
0
multiple instances? Updated
Your query has actually been answered more than once. You don't need to
define mounts in the icecast.xml file, the source clients (which connect
to icecast and stream music to it) define the mount point by virtue of
connecting to it. I use liquadsoap as a source client, and I set the
mount point in liquadsoap to "jake-radio.mp3" like this:
-------- 8< --------
2002 Apr 23
16
[Bug 194] still problems with libutil
http://bugzilla.mindrot.org/show_bug.cgi?id=194
------- Additional Comments From djm at mindrot.org 2002-04-23 23:29 -------
This should be fixed in -current CVS, please test
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2014 Oct 14
1
[OT]] CentOS 7 docs, tutorials, etc...
I apologize in advance for the subject and length of this reply. I debated
just letting things pass without comment. But, security has many levels. And
the first level is recognition of the threat.
Whether we recognize it or not. Whether we agree of disagree with the politics
that lie beneath this situation or not; Whether we consider this a
non-technical issue or not; By virtue of our
2019 Sep 10
7
multiple instances? Updated
Hello, Thomas_B._Rücker,
Initially I was asking for a working example file with more than one stream instance. Something that I can take as an example to work from.
I've not gotten that yet, despite posting 2 config files; both that came with the install package.
Trust me, if there were other choices for streaming servers than just icecast and shoutcast; I'd be running there to see if