Displaying 20 results from an estimated 21 matches for "syslog_serv".
Did you mean:
syslog_server
2007 Jun 04
5
Virtual defines ?
...path => "/etc/syslog-ng/syslog-ng.conf",
owner => "root",
group => "root",
mode => 440,
backup => main,
source => $source,
notify => Service[syslog-ng]
}
}
then i define 2 classes:
class syslog_server {
syslog_ng { "server": source =>"puppet://puppet/dist/apps/
syslog-ng/syslog-server.conf" }
}
class syslog_client{
syslog_ng { "client": source => "puppet://puppet/dist/apps/
syslog-ng/syslog-client.conf" }
}
My problem is that i Want...
2009 Jul 13
1
[PATCH node] Adds vlan support to auto-installations for the node. bz#511056
...ateway=
ipv6=
@@ -344,6 +346,9 @@ start() {
hostname=*)
hostname=${i#hostname=}
;;
+ vlan=*)
+ vlan=${i#vlan=}
+ ;;
syslog=*)
i=${i#syslog=}
eval $(printf $i|awk -F: '{print "syslog_server="$1; print "syslog_port="$2;}')
@@ -365,7 +370,7 @@ start() {
ip_gateway=$gateway
fi
# save boot parameters as defaults for ovirt-config-*
- params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size l...
2011 Jul 21
0
[PATCH] add netconsole autoinstall parameter
...set /files/etc/sysconfig/netconsole/SYSLOGADDR $OVIRT_NETCONSOLE_SERVER
+set /files/etc/sysconfig/netconsole/SYSLOGPORT $OVIRT_NETCONSOLE_PORT
+EOF
+ ovirt_store_config /etc/sysconfig/netconsole
+}
# AUTO for auto-install
if [ "$1" = "AUTO" ]; then
if [ -z "$OVIRT_SYSLOG_SERVER" -o -z "$OVIRT_SYSLOG_PORT" ]; then
@@ -189,6 +196,10 @@ if [ "$1" = "AUTO" ]; then
printf "\nUsing default syslog server '$OVIRT_SYSLOG_SERVER:$OVIRT_SYSLOG_PORT'.\n"
ovirt_rsyslog $OVIRT_SYSLOG_SERVER $OVIRT_SYSLOG_PORT udp...
2009 Jul 21
0
[PATCH node] Adds a new kernel cmdline argument to toggle SSH password auth.
...-349,6 +351,12 @@ start() {
vlan=*)
vlan=${i#vlan=}
;;
+ ssh=1 | ssh=true)
+ ssh=true
+ ;;
+ ssh=0 | ssh=false)
+ ssh=false
+ ;;
syslog=*)
i=${i#syslog=}
eval $(printf $i|awk -F: '{print "syslog_server="$1; print "syslog_port="$2;}')
@@ -370,7 +378,7 @@ start() {
ip_gateway=$gateway
fi
# save boot parameters as defaults for ovirt-config-*
- params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size l...
2009 Jul 22
1
Updated patch...
This patch obsoletes the previous, renaming the karg to ssh_pwauth.
2009 Jul 22
1
Changes the ssh karg to ssh_pwauth
This patch obsoletes the previous one with feedback from pmyers at redhat.com.
2009 Nov 16
3
[PATCH] Add support for vendor hooks during ovirt-early start()
...p_gateway=$gateway
fi
# save boot parameters as defaults for ovirt-config-*
- params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size local_boot standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp vlan ssh_pwauth syslog_server syslog_port collectd_server collectd_port bootparams hostname firstboot"
+ # and allow vendor prehook set params to be saved
+ params="${params} bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size local_boot standalone overcommit ip...
2007 Jun 07
3
Provisioning Linksys PAP2T ATA's
Does anyone know how the Linksys PAP2T ATA's can be mass provisioned?
Documentation seems to be sketchy, even on the Linksys web site.
Thanks,
Doug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070607/3f90695c/attachment.htm
2009 Nov 16
1
Refactored upgrade patch...
This patch includes feedback from apevec to remain backward compatible
with the previous karg, ovirt_local_boot.
2009 Nov 13
1
[PATCH] Provides an explicit upgrade path for an installed node.
...p_gateway=$gateway
fi
# save boot parameters as defaults for ovirt-config-*
- params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size local_boot standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp vlan ssh_pwauth syslog_server syslog_port collectd_server collectd_port bootparams hostname firstboot"
+ params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size upgrade standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp vlan ssh_pwauth syslog_s...
2009 Nov 16
2
Resend...
Resending the refactored patch: I realized after I emailed it that it
referenced the wrong bugzilla.
2010 Jul 21
0
[PATCH] RFC: Encrypted swap support
...ave boot parameters as defaults for ovirt-config-*
- params="bootif init initapp vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size vol_swap2_size vol_data2_size upgrade standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp vlan ssh_pwauth syslog_server syslog_port collectd_server collectd_port bootparams hostname firstboot runtime_mode"
+ params="bootif init initapp vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size vol_swap2_size vol_data2_size crypt_swap crypt_swap2 upgrade standalone overcom...
2009 May 20
2
[PATCH node] Adds support for a core dump partition to the node.
...t() {
ip_gateway=$gateway
fi
# save boot parameters as defaults for ovirt-config-*
- params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size local_boot standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp syslog_server syslog_port collectd_server collectd_port bootparams hostname firstboot"
+ params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_coredump_size vol_data_size local_boot standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp sys...
2009 Dec 13
13
Inherited Client and Server Apps
So, I''ve been doing something like this for applications that have a
client and server component...
node base_node {
include syslog_ng::client
}}
node app_node inherits base_node {
}
node syslog_server inherits base_node {
include syslog_ng::server
}
... because I want the client portion, syslog-ng in this case to be
installed on everything. However, the server node also has a server
running. When you do this, puppet complains because on the
syslog_server node, both are trying to manage the...
2009 Oct 01
1
Repost of Patch 6/6 for ovirt-node
All other patches from the sequence remain unchanged. Repost of patch 6 based on comments from Joey to follow.
Mike
2010 Jul 21
0
[PATCH] RFC: Advanced Storage Configuration
...ip_gateway=$gateway
fi
# save boot parameters as defaults for ovirt-config-*
- params="bootif init vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size upgrade standalone overcommit ip_address ip_netmask ip_gateway ipv6 dns ntp vlan ssh_pwauth syslog_server syslog_port collectd_server collectd_port bootparams hostname firstboot runtime_mode"
+ params="bootif init initapp vol_boot_size vol_swap_size vol_root_size vol_config_size vol_logging_size vol_data_size vol_swap2_size vol_data2_size upgrade standalone overcommit ip_address ip_netma...
2009 Sep 26
10
Adding handling for Multipath storage devices
The following patches introduce support for multipath and cciss devices to the ovirt-node and node-image. Comments are appreciated.
These patches assume that the 3 patches (2 node, 1 node-image) from Joey are all incorporated.
Mike
2009 Jan 20
2
PAP2T provisioning
Anyone have an example XML file for the PAP2T?
Cheers,
j
2008 Jan 26
5
autoprovision 200+ linksys phones setup
Hi there,
We have plans to install an office (not call center) with the following setup:
200 linksys 942 phones (sip + g711) on a LAN
a server with a dual port E1 sangoma and a remora card with 4 fxo modules.
So far when we want to setup a linksys phone, we need to use the http
interface of each phone, disable/enable a lot of things and plug it
into the network. this is not the best scenario for
2010 Feb 10
1
RFC: First pass at making the node generic...
I'm looking for feedback on this first patch. The node has been pushed
towards a more generic boot process. With this patch the node can now
boot up and execute a few specifically-named scripts that reside in
/etc/node.d/ at key points during the startup.
After this goes upstream, the next step will be to define in more detail
the remote interfaces for the "managed" runtime