Hello,
I am using dual boot of linux, one is ubuntu and the other is one is centos.
I have three NIC's and only one of them connected with cable.
The thing is that when I boot from the ubuntu, it does recognize it and I am connected to the Internet.
When I boot from the centos I am not... (6 Replies)
I am having a bit of trouble getting my CENTOS 6.5 DNS server to work correctly in our testlab environment. Lab network is 10.8.0.0/24 in which we all access from 10.7.0.0.0/24 && 10.0.0.0/24. Here are my configs:
options {
listen-on port 53 { 127.0.0.1; 10.8.0.19;};
#listen-on-v6 port 53 {... (2 Replies)
I attempted to update Python on my CentOS 5.6 VM and have encountered some issues after then. Initially yum wouldn't work, but I have resolved that.
However, now I am unable to access the Network Configuration section under setup.
When I do select this option I see this at the command line:
... (2 Replies)
Hello,
Today, i just updated my Openvas server for latest NVT, portsname and scapdata but after that i am not able to login to my openvas instance.
Below command i fired to get this done.
openvas-nvt-sync
openvas-certdata-sync
openvas-portnames-update
openvas-scapdata-sync... (0 Replies)
Hallo to everyone.From sometime i have problems with my asterisk pbx on cent os which is in corosync cluster mode with resource groups.The problem is for time the cluster just swap the active one with the other and the only messages in \var\log\messages is that bond0:link status defenitly down for... (0 Replies)
Hello,
We are migrating our gateways from CentOS 6 to CentOS 7 and for setting up a transparent proxy using squid and Firewalld i am using below configuration.
#Firewalld configurations
firewall-cmd --permanent --zone=public --add-forward-port=port=80:proto=tcp:toport=3128:toaddr=LAN_IP... (4 Replies)
Hello,
Did anyone setup a CentOS7 as a gateway (with squid transparent proxy).
I am trying to do so but not able to setup.
I setup squid , iptables (using it instead of firewalld) and all the necessary IPtables rules but nothing work.
It work previously but access.log of squid not getting... (4 Replies)
Discussion started by: sunnysthakur
4 Replies
LEARN ABOUT DEBIAN
slack.conf
slack.conf(5) File Formats Manual slack.conf(5)NAME
slack.conf - configuration file for slack
DESCRIPTION
The file /etc/slack.conf contains configuration information for slack(8) and its backends. It should contain one keyword-value pair per
line, separated by an '=' sign. Keywords must consist solely of capital letters and underscores. Values may take any appropriate format,
but must not begin with a space. Comments start with '#', and all text from the '#' to the end of a line is ignored. Trailing whitespace
on lines is ignored. Empty lines or lines consisting of only whitespace and comments are ignored.
Valid keywords are:
SOURCE The master source for slack roles. It can be in one of four forms:
o /path/to/dir
Use a local directory.
o somehost:/path/to/dir
Use given directory on a remote host via rsync over SSH.
o rsync://somehost/module
Use module on a remote rsyncd server (directly over the network).
o somehost::module
Use the rsync daemon protocol over SSH to the given host. See "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION" in
rsync(1)
All forms of SOURCE are passed directly to rsync, so you can do things like add "user@" before the host on any remote forms. For
more about what rsync can do, see its manual page, of course.
For the last form, however, we do a little magic. rsync treats the last two forms equivalently, so we overload the last form by
automatically passing "-e ssh" to rsync when we see it. This hack lets us tell slack to use this nice feature of rsync just using
the SOURCE config option.
ROOT The root filesystem into which to install slack roles. Usually '/'.
ROLE_LIST
The location of the role list, which lists the roles to be installed by default on each host.
This can be a path relative to the source, or can be an entirely separate location if it starts with a slash or a hostname (option-
ally preceeded by user@).
CACHE A local cache directory, used as a local mirror of the SOURCE.
STAGE A local staging directory, used as an intermediate stage when installing files.
BACKUP_DIR
A directory in which to keep dated backups for rollbacks.
EXAMPLE
A typical file might look like this:
# slack.conf configuration file
SOURCE=slack-master:/slack # source is on a remote
# host named "slack-master"
ROLE_LIST=slack-master:/roles.conf
ROOT=/
CACHE=/var/cache/slack
STAGE=/var/lib/slack/stage
BACKUP_DIR=/var/lib/slack/backups
FILES
/etc/slack.conf
SEE ALSO slack(8), rsync(1)File formats 2005-05-23 slack.conf(5)