Always use 'lib' instead of 'lib64'

[vpp.git] / extras / vpp_config / data / startup.conf.template

diff --git a/extras/vpp_config/data/startup.conf.template b/extras/vpp_config/data/startup.conf.template
index 91b92c6..22b0e12 100644 (file)
--- a/extras/vpp_config/data/startup.conf.template
+++ b/extras/vpp_config/data/startup.conf.template
@@ -1,7 +1,7 @@
 
 unix {{
 {unix}
-  log /tmp/vpp.log
+  log /var/log/vpp/vpp.log
   full-coredump
   cli-listen /run/vpp/cli.sock
 }}
@@ -12,8 +12,8 @@ api-trace {{
 
 cpu {{
 {cpu}
-  scheduler-policy fifo
-  scheduler-priority 50
+  # scheduler-policy fifo
+  # scheduler-priority 50
 
         ## In the VPP there is one main thread and optionally the user can create worker(s)
        ## The main thread and worker thread(s) can be pinned to CPU core(s) manually or automatically
@@ -114,10 +114,10 @@ dpdk {{
 # Adjusting the plugin path depending on where the VPP plugins are:
 #plugins
 #{{
-#      path /home/bms/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins
+#      path /home/bms/vpp/build-root/install-vpp-native/vpp/lib/vpp_plugins
 #}}
 
 # Alternate syntax to choose plugin path
-#plugin_path /home/bms/vpp/build-root/install-vpp-native/vpp/lib64/vpp_plugins
+#plugin_path /home/bms/vpp/build-root/install-vpp-native/vpp/lib/vpp_plugins
 
 {tcp}