Are typical camera bag materials enough for non weather sealed DSLR in 5 minutes of medium rain?

I have a non weather sealed DSLR (Canon 2000D) along with a bunch of non weather sealed lenses and other equipment. I am for obvious reasons not planning to use the camera outdoors in rain, snow or similar weather.

However, I may have to move the camera in the bag to another indoors location in rain.

Today, I learned that many “all weather” camera bags have separate raincovers you have to put on. So, it’s not the main material that is weather-resistant but rather a separate raincover.

Do typical camera bag materials (apart from the separate raincover) keep the equipment inside dry enough during a 5 minute walk in medium rain? In very heavy rain, I can of course use the separate raincover but I would prefer a camera bag that is built from material that keeps the camera adequately dry in medium rain for short periods of time. I understand that most camera bags are built from nylon and polyester.

SSH takes more than 2 minutes for password prompt

I went through some of the thread on the same issue. But I am new to Linux and I ran the -vvv command while ssh-ing. As ssh is taking so long my ansible application takes even longer to execute. Can someone please help me understand and resolve the issue.

netman@netman:~$   ssh root@172.16.1.2 -vvv OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "172.16.1.2" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to 172.16.1.2 [172.16.1.2] port 22. debug1: Connection established. debug1: identity file /home/netman/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /home/netman/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/netman/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/netman/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/netman/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/netman/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/netman/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/netman/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4 debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to 172.16.1.2:22 as 'root' debug3: hostkeys_foreach: reading file "/home/netman/.ssh/known_hosts" debug3: record_hostkey: found key type ECDSA in file /home/netman/.ssh/known_hosts:4 debug3: load_hostkeys: loaded 1 keys from 172.16.1.2 debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib@openssh.com,zlib debug2: compression stoc: none,zlib@openssh.com,zlib debug2: languages ctos:  debug2: languages stoc:  debug2: first_kex_follows 0  debug2: reserved 0  debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,cast128-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,cast128-cbc,3des-cbc debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,zlib@openssh.com debug2: compression stoc: none,zlib@openssh.com debug2: languages ctos:  debug2: languages stoc:  debug2: first_kex_follows 0  debug2: reserved 0  debug1: kex: algorithm: curve25519-sha256@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug3: send packet: type 30 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: Server host key: ecdsa-sha2-nistp256 SHA256:x5OIBrhQUhm2sDiS4X4w/s1hueWiVLGMYqt1QpMexLI debug3: hostkeys_foreach: reading file "/home/netman/.ssh/known_hosts" debug3: record_hostkey: found key type ECDSA in file /home/netman/.ssh/known_hosts:4 debug3: load_hostkeys: loaded 1 keys from 172.16.1.2 debug1: Host '172.16.1.2' is known and matches the ECDSA host key. debug1: Found key in /home/netman/.ssh/known_hosts:4 debug3: send packet: type 21 debug2: set_newkeys: mode 1 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: SSH2_MSG_NEWKEYS received debug2: set_newkeys: mode 0 debug1: rekey after 134217728 blocks debug2: key: /home/netman/.ssh/id_rsa (0x1b93f48), agent debug2: key: /home/netman/.ssh/id_dsa ((nil)) debug2: key: /home/netman/.ssh/id_ecdsa ((nil)) debug2: key: /home/netman/.ssh/id_ed25519 ((nil)) debug3: send packet: type 5 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 debug3: receive packet: type 51 debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure.  Minor code may provide more information No Kerberos credentials available  debug1: Unspecified GSS failure.  Minor code may provide more information No Kerberos credentials available  debug1: Unspecified GSS failure.  Minor code may provide more information   debug1: Unspecified GSS failure.  Minor code may provide more information No Kerberos credentials available  debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /home/netman/.ssh/id_rsa debug3: send_pubkey_test debug3: send packet: type 50 debug2: we sent a publickey packet, wait for reply debug3: receive packet: type 60 debug1: Server accepts key: pkalg rsa-sha2-512 blen 279 debug2: input_userauth_pk_ok: fp SHA256:9fpXTLOlPwBVclWhuK5zclhQ7GlDxFqa9dnWbZPKzPo debug3: sign_and_send_pubkey: RSA SHA256:9fpXTLOlPwBVclWhuK5zclhQ7GlDxFqa9dnWbZPKzPo debug3: send packet: type 50 debug3: receive packet: type 52 debug1: Authentication succeeded (publickey). Authenticated to 172.16.1.2 ([172.16.1.2]:22). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug3: send packet: type 90 debug1: Requesting no-more-sessions@openssh.com debug3: send packet: type 80 debug1: Entering interactive session. debug1: pledge: network debug3: receive packet: type 80 debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0 debug3: receive packet: type 91 debug2: callback start debug2: fd 3 setting TCP_NODELAY debug3: ssh_packet_set_tos: set IP_TOS 0x10 debug2: client_session2_setup: id 0 debug2: channel 0: request pty-req confirm 1 debug3: send packet: type 98 debug1: Sending environment. debug3: Ignored env XDG_VTNR debug3: Ignored env XDG_SESSION_ID debug3: Ignored env XDG_GREETER_DATA_DIR debug3: Ignored env CLUTTER_IM_MODULE debug3: Ignored env SESSION debug3: Ignored env GPG_AGENT_INFO debug3: Ignored env TERM debug3: Ignored env VTE_VERSION debug3: Ignored env SHELL debug3: Ignored env QT_LINUX_ACCESSIBILITY_ALWAYS_ON debug3: Ignored env WINDOWID debug3: Ignored env OLDPWD debug3: Ignored env UPSTART_SESSION debug3: Ignored env GNOME_KEYRING_CONTROL debug3: Ignored env GTK_MODULES debug3: Ignored env USER debug3: Ignored env LS_COLORS debug3: Ignored env QT_ACCESSIBILITY debug3: Ignored env UNITY_HAS_3D_SUPPORT debug3: Ignored env XDG_SESSION_PATH debug3: Ignored env XDG_SEAT_PATH debug3: Ignored env SSH_AUTH_SOCK debug3: Ignored env DEFAULTS_PATH debug3: Ignored env LIBVIRT_DEFAULT_URI debug3: Ignored env XDG_CONFIG_DIRS debug3: Ignored env UNITY_DEFAULT_PROFILE debug3: Ignored env DESKTOP_SESSION debug3: Ignored env PATH debug3: Ignored env QT_IM_MODULE debug3: Ignored env QT_QPA_PLATFORMTHEME debug3: Ignored env XDG_SESSION_TYPE debug3: Ignored env PWD debug3: Ignored env JOB debug3: Ignored env XMODIFIERS debug3: Ignored env GNOME_KEYRING_PID debug1: Sending env LANG = en_US.UTF-8 debug2: channel 0: request env confirm 0 debug3: send packet: type 98 debug3: Ignored env GDM_LANG debug3: Ignored env MANDATORY_PATH debug3: Ignored env COMPIZ_CONFIG_PROFILE debug3: Ignored env IM_CONFIG_PHASE debug3: Ignored env GDMSESSION debug3: Ignored env SESSIONTYPE debug3: Ignored env GTK2_MODULES debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env XDG_SEAT debug3: Ignored env LANGUAGE debug3: Ignored env LIBGL_ALWAYS_SOFTWARE debug3: Ignored env GNOME_DESKTOP_SESSION_ID debug3: Ignored env UPSTART_INSTANCE debug3: Ignored env UPSTART_EVENTS debug3: Ignored env XDG_SESSION_DESKTOP debug3: Ignored env LOGNAME debug3: Ignored env COMPIZ_BIN_PATH debug3: Ignored env DBUS_SESSION_BUS_ADDRESS debug3: Ignored env XDG_DATA_DIRS debug3: Ignored env QT4_IM_MODULE debug3: Ignored env LESSOPEN debug3: Ignored env INSTANCE debug3: Ignored env UPSTART_JOB debug3: Ignored env XDG_RUNTIME_DIR debug3: Ignored env DISPLAY debug3: Ignored env XDG_CURRENT_DESKTOP debug3: Ignored env GTK_IM_MODULE debug3: Ignored env LESSCLOSE debug3: Ignored env XAUTHORITY debug3: Ignored env _ debug2: channel 0: request shell confirm 1 debug3: send packet: type 98 debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: receive packet: type 99 debug2: channel_input_status_confirm: type 99 id 0 debug2: PTY allocation request accepted on channel 0 debug2: channel 0: rcvd adjust 2097152 debug3: receive packet: type 99 debug2: channel_input_status_confirm: type 99 id 0 debug2: shell request accepted on channel 0 Last login: Sat Mar 16 08:05:46 2019 from gateway [root@localhost ~]#  [root@localhost ~]#  [root@localhost ~]#  [root@localhost ~]#  [root@localhost ~]# logoutdebug3: receive packet: type 98 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug3: receive packet: type 98 debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0 debug2: channel 0: rcvd eow debug2: channel 0: close_read debug2: channel 0: input open -> closed  debug3: receive packet: type 96 debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed debug3: receive packet: type 97 debug2: channel 0: rcvd close debug3: channel 0: will not send data after close debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug3: send packet: type 97 debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open:   #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)  debug3: send packet: type 1 Connection to 172.16.1.2 closed. Transferred: sent 3224, received 3292 bytes, in 280.5 seconds Bytes per second: sent 11.5, received 11.7 debug1: Exit status 0 netman@netman:~$    

Android Terminal disabled for ~2 minutes after booting phone

After booting my Android mobile phone, jackpal.androidterm terminal app does not prompt. It just remains a black screen. All other apps start as usual.

In addition, the window number (“Window 1”) is not displayed.

After waiting one to two minutes, it suddenly starts working as usual.

All other applications start and work as usual after boot.

How come Android Terminal is disabled for the first two minutes after boot?

SQL dumping all pages from buffer cache every few minutes

I have a single SQL2012 SP4 node running several databases.

The server has 20GB of memory available, 14GB allocated to SQL (nothing else running on the box).

Every few minutes SQL dumps the whole of the buffer cache. Page life expectancy hits zero, the buffer cache descriptors show that there’s nothing in the cache.

I had a look at the resource monitor notifications and the notifications are bouncing around from high/steady/low every few milliseconds:

RESOURCE_MEMPHYSICAL_HIGH RESOURCE_MEM_STEADY RESOURCE_MEMPHYSICAL_LOW

With timestamps that are several milliseconds apart. The PLE is essentially a saw-tooth pattern.

I’ve seen this happen before with SQL2012 SP1 and this question:

SQL Server 2012 Free Pages in Buffer Cache Not Being Used

Seems to be a similar issue, though I’ve already updated to SP4.

I’ve tried turning on LPIM for the service account and I’ve tried messing with the max memory setting. Lowering max memory seems to have caused the buffer cache to empty more frequently.

Any ideas of what to check next?

Server workload is literally nothing (I’m scrolling through lists of items in an ERP system and it gets to about 40-50MB before the cache just drops again).

It’s interesting because I upgraded from SP1 to try and fix this – the cache there was getting to around 500MB. Since then I dropped the max memory setting to 14GB which seems to have made it worse.

I’m wondering if Windows is panicking and throwing incorrect notifications for memory pressure at SQL – it follows that the server with max memory set to unbounded seemed to run ok-ish but never fill the cache more than a few hundred MB – but now it barely gets to 50…

Upon submitting a webform, set a date field on the article node equals to “current time” + “X minutes”

I am using the Field Timer module to display countdown timer on my article node.

This module will take the value of the date/time field (my case: field_article_datetime) and convert it into a countdown timer in the display of the article.

I have a webform (machine name: ABC) attached as a field to the article content type so I can use [webform_submission:node:nid] to retrieve the article nid of the article to be updated.

The webform (machine name: ABC) has below element:

1) Select element (machine name: increase_time_in_minutes):

  1. Text: Increase by 15 minutes (Value: 15)
  2. Text: Increase by 30 minutes (Value: 30)
  3. Text: Increase by 45 minutes (Value: 45)

And the article content type has below field:

  1. date/time field (machine name: field_article_datetime) (the Field Timer module is applied to this field)

When the webform “ABC” is submitted, I want to:

  1. Fetch the article nid ([webform_submission:node:nid])
  2. Set the value of the date/time field (field_article_datetime) equal to current time + increase_time_in_minutes

EXAMPLE:

Say at 14/03/2019 08:30:15 PM, a user has submitted the webform “ABC” and selected Increase by 15 minutes option from the select list… So I need the related article to be fetched and update the (field_article_datetime) to have the value of 14/03/2019 08:45:15 PM

This way, the user will see a countdown timer for 15 minutes on the article node display page.


I am not a programmer, but I think the best Idea is to use a customwebformhandler.php file which will be enabled for the webform settings page.

I have created the file but I need help to finish it:

<?php  namespace Drupal\my_module_name\Plugin\WebformHandler;  use Drupal\Core\Session\AccountInterface; use Drupal\Core\Serialization\Yaml; use Drupal\Core\Form\FormStateInterface;  use Drupal\node\Entity\Node;  use Drupal\webform\WebformInterface; use Drupal\webform\Plugin\WebformHandlerBase; use Drupal\webform\webformSubmissionInterface; use Drupal\webform\Entity\WebformSubmission;   /**  * Update a node entity from a webform submission.  *  * @WebformHandler(  *   id = "Update a node",  *   label = @Translation("Update a node"),  *   category = @Translation("Entity Update"),  *   description = @Translation("Updates a node from Webform Submissions."),  *   cardinality = \Drupal\webform\Plugin\WebformHandlerInterface::CARDINALITY_UNLIMITED,  *   results = \Drupal\webform\Plugin\WebformHandlerInterface::RESULTS_PROCESSED,  *   submission = \Drupal\webform\Plugin\WebformHandlerInterface::SUBMISSION_REQUIRED,  * )  */  class UpdateNodeWebformHandler extends WebformHandlerBase {    /**    * {@inheritdoc}    */    // Fetch & Update node object from webform-submission.    // Function to be fired while submitting the Webform.   public function submitForm(array &$  form, FormStateInterface $  form_state, WebformSubmissionInterface $  webform_submission) {     // Get an array of the values from the submission.     $  values = $  webform_submission->getData();      // This is the part where to fetch the article node.         SOME CODES GOES HERE.      // This is the node Updating part.        SOME CODES GOES HERE.      // This is the node Saving part.     $  node->save();   } } 

Set a date field equal to “current time + 5 minutes” using tokens

I am using the Field Timer module to display countdown timer on my article node.

Say my article node has the date/time field named (field_article_datetime)

This module will take the value of the date/time field (field_article_datetime) and convert it into a countdown timer in the display of the article.

When the article node is created, I want to set the value of the date/time field (field_article_datetime) equal to current time + 5 minutes.

To extract the current time, I am using the token [node:created] from the token module, but I cannot find a solution on how to add +5 minutes to the token [node:created].

EXAMPLE:

Say at 12/03/2019 08:50:15 PM, a user has created a new article node… So I need a solution to add +5 minutes to the created time so the date/time field named (field_article_datetime) will be equal to 12/03/2019 08:55:15 PM

This way, the user will see a countdown timer for 5 minutes on the article node display page.

Note: I am using the Business Rules module (similar to Rules module) to set the value of the date/time field (field_article_datetime) with the help of the token module.

Why is it common in European airports not to display the gate for flights until around 45-90 minutes before departure, unlike other places?

https://youtu.be/wdU1WTBJMl0?t=262 mentions:

00:04:22: Heathrow also doesn’t display the gate for flights until around 45-90 minutes before departure. This is common in European airports, but uncommon elsewhere.

Why is it common in European airports not to display the gate for flights until around 45-90 minutes before departure, unlike other places?