13%
15.12.2017
08 action :install
09 end
10 service "apache2" do
11 action [ :enable, :start ]
12 end
13
14 directory node['main']['doc_root'] do
15 owner 'www1-data'
16 group 'www1-data'
17 mode '0744'
18 action
13%
18.03.2012
Name
------- ------ ----- ----- ----- ------ -- -----------
81 9 2392 3076 76 0.12 3996 AmIcoSinglun64
74 9 1464 2568 42 0.09 2172 armsvc
195 10 2380 2984 62
13%
28.11.2023
the teams' responsibilities (a team implements at least one bounded context but can implement more than one); (2) between the requirements (e.g., as a separate backlog for each bounded context); (3
13%
30.11.2025
: {$Ticket->OwnerObj->Name}
09 Requestor: {$Ticket->Requestors->EmailsAsString()}
10 Ticket URL: {$RT::WebURL}Ticket/Display.html?id={$Ticket->id}
11
12 Please check the content. If everything turns out
13%
17.02.2015
int idparticle;
05 double pos[D];
06 double vel[D];
07 double force0[D];
08 double force[D];
09 double mass;
10 char bf[BFSIZE];
11 void *nxtParticle;
12 };
13 PARTICLE
13%
11.10.2016
-server"}))
06
07 ; Enable all interfaces for TCP, UDP and websockets:
08 (let [host "0.0.0.0"]
09 (tcp-server {:host host})
10 (udp-server {:host host})
11 (ws-server {:host host}))
12
13 ; Clean up events
13%
20.05.2014
daily
05 missingok
06 notifempty
07 compress
08 delaycompress
09 sharedscripts
10 postrotate
11 invoke-rc.d rsyslog reload > /dev/null
12 endscript
13 }
Finally, to see the syslog
13%
17.06.2017
Software services packaged as containers finally reached the remotest corners of IT about three years ago. Docker [1], rkt [2], LXC [3], and the like see themselves confronted with technologies
13%
13.06.2016
='netfs'>
02
virtstore
03
04
05
06
07
08
09
13%
30.01.2024
usually takes place within 12 hours but is by no means even close to real time. That said, you can see on the portal that the command has taken effect after just a few minutes; the status of Azure AD
