Changeset 43362 in vbox
- Timestamp:
- Sep 20, 2012 8:37:33 AM (12 years ago)
- File:
-
- 1 edited
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r42733 r43362 1060 1060 /sbin/sysctl -p</screen></para> 1061 1061 1062 <para>The above commands will add the new limits to the config file, thus1062 <para>The above commands will add the new limits to the configuration file, thus 1063 1063 making the effect persistent across reboots, and will activate the new 1064 1064 limits into the currently running kernel.</para> … … 1159 1159 syntax is used. Keep in mind that on Windows hosts a named pipe must 1160 1160 always start with <computeroutput>\\.\pipe\</computeroutput>. On Linux the 1161 same config settings apply, except that the path name for the1161 same configuration settings apply, except that the path name for the 1162 1162 <computeroutput>Location</computeroutput> can be chosen more freely. Local 1163 1163 domain sockets can be placed anywhere, provided the user running … … 2288 2288 during boot to determine whether to allow individual users to start a VM 2289 2289 automatically and configure startup delays. 2290 The config file can be placed in <computeroutput>/etc/vbox</computeroutput>2290 The configuration file can be placed in <computeroutput>/etc/vbox</computeroutput> 2291 2291 and contains several options. One is <computeroutput>default_policy</computeroutput> 2292 2292 which controls whether the autostart service allows or denies to start a VM
Note:
See TracChangeset
for help on using the changeset viewer.

