13%
05.02.2019
Host *:80>
02 ServerAdmin webmaster@localhost
03 ServerName localhost
04
05 DocumentRoot /var/www/suitecrm/
06
07 Options FollowSymLinks
08 AllowOverride None
09
13%
05.02.2023
entity = {
04 key: taskKey,
05 data: [
06 {
07 name: 'created',
08 value: new Date().toJSON(),
09 },
10 {
11 name: 'description',
12 value
13%
14.03.2013
,
09 sizeof(j));
10 [...]
11 MALLOC(pr, struct prison *,
12 sizeof(*pr),
13 M_PRISON, M_WAITOK | M_ZERO);
14 [...]
15 error = copyinstr(j.path,
16 &pr->pr_path, sizeof
13%
18.07.2013
rq2 ra92
08 set rq3 cdrom
09
10 attach rq0 d0.dsk
11 attach rq1 d1.dsk
12 attach rq2 d2.dsk
13
14 attach -r rq3 cdrom.iso
15
16 set rl disable
17 set ts disable
18
19 set xq mac=08-00-2B-AA-BB-CC
20
13%
11.04.2016
network adapters, one for administration and one for the web server. I gave the system 1GB memory, but it has not yet used more than 200MB.
Then, boot the image. You have several choices:
Add
13%
14.08.2017
storage is handled by the almost venerable ext3. The use of BusyBox [11] for most executable programs and of Dropbear [12] as the SSH daemon is the logical consequence of the Buildroot underpinnings
13%
05.12.2016
_Master_Log_Pos: 140927111
09 Relay_Log_File: mysqld-relay-bin.000002
10 Relay_Log_Pos: 11109399
11 Relay_Master_Log_File: mariadb-bin.000008
12 Slave_IO_Running: Yes
13
12%
22.08.2011
[inst.id] = inst.state
08 summary[inst.state] += 1
09 state
10 end
11 total = summary.values.inject(0) { |sum, i| sum += i }
12 puts "Found #{total} instances in the following states:"
13 summary
12%
30.11.2025
another could allow the user to set up memory of between 1 and 8GB in increments of 512MB.
The Deltacloud API bundles all these possibilities into hardware profiles, which means the clients are provided
12%
30.11.2025
starter kit: https://www.icinga.org/2010/09/22/starter-kit-icinga-virtual-appliance/
Zabbix appliance: http://www.vmware.com/appliances/directory/353
