Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #17735 > unrolled thread

php ini

Back to article view | Back to comp.lang.php

Contents

  php ini madwomans Dad <dsvirtual58@gmail.com> - 2018-05-16 13:09 +0100
    Re: php ini tony@mountifield.org (Tony Mountifield) - 2018-05-16 13:11 +0000
      Re: php ini K <yyyyyeeeee00000@writeme.com> - 2023-03-11 07:53 -0800
        Re: php ini doctor@doctor.nl2k.ab.ca (The Doctor) - 2023-03-11 23:44 +0000
    Re: php ini Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2018-05-16 10:38 -0400
      Re: php ini Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-05-16 16:53 +0200
        Re: php ini Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2018-05-16 12:02 -0400
          Re: php ini Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-05-16 19:59 +0200
            Re: php ini Jerry Stuckle <jstucklex@attglobal.net> - 2018-05-16 15:09 -0400
      Re: php ini "J.O. Aho" <user@example.net> - 2018-05-16 18:29 +0200
    Re: php ini Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2018-05-16 16:48 +0200
      Re: php ini "J.O. Aho" <user@example.net> - 2018-05-16 18:36 +0200
    Re: php ini madwomans Dad <dsvirtual58@gmail.com> - 2018-05-17 08:42 +0100

#17735 — php ini

I'm trying to find out if it's possible to configure session timeout in 
some ini file

$ php -version
PHP 7.1.14 (cli) ...


$ cat  ./opt/alt/php71/etc/php.ini | grep session

I can see all sorts of stuff but what I want is something in the ini 
file like session.timeout=whatever

I really don't want to have to do this in code.

Is there a 'secret' way to do this in the/an/some ini file

Thanks

madwomans Dad

[toc] | [next] | [standalone]

#17736

In article <pdh718$u78$1@dont-email.me>,
madwomans Dad  <dsvirtual58@gmail.com> wrote:
> I'm trying to find out if it's possible to configure session timeout in 
> some ini file
> 
> $ php -version
> PHP 7.1.14 (cli) ...
> 
> 
> $ cat  ./opt/alt/php71/etc/php.ini | grep session
> 
> I can see all sorts of stuff but what I want is something in the ini 
> file like session.timeout=whatever
> 
> I really don't want to have to do this in code.
> 
> Is there a 'secret' way to do this in the/an/some ini file

Not specifically, as far as I can tell.

First you need to define what you mean by "session timeout". It could
easily mean one of two things:

1. The maximum duration of a session. So a session would be destroyed
   a specified time after it was first created, even if it was in use.

2. The length of time after a session's last use that it will be discarded.
   So a session would continue to exist as long as it was used again within
   the timeout period, but would be destroyed if not used again within the
   timeout.

There doesn't appear to be a php.ini setting specifically for either scenario.
There are some statistical garbage collection settings for cleaning up old
sessions when using a global file-based session store. But they are basically
resource management rather than hard lifetime enforcement.

Cheers
Tony
-- 
Tony Mountifield
Work: tony@softins.co.uk - http://www.softins.co.uk
Play: tony@mountifield.org - http://tony.mountifield.org

[toc] | [prev] | [next] | [standalone]

#19398

Get to watch Jesus videos !

youtu.be/-3nN9-C1yKU

...
......
...........
.........................
.......................................
...................................................
.....................................................................
.............................................................................................




On Wednesday, May 16, 2018 at 3:11:23 PM UTC+2, Tony Mountifield wrote:
> In article <pdh718$u78$1...@dont-email.me>,
> madwomans Dad <dsvir...@gmail.com> wrote: 
> > I'm trying to find out if it's possible to configure session timeout in 
> > some ini file 
> > 
> > $ php -version 
> > PHP 7.1.14 (cli) ... 
> > 
> > 
> > $ cat ./opt/alt/php71/etc/php.ini | grep session 
> > 
> > I can see all sorts of stuff but what I want is something in the ini 
> > file like session.timeout=whatever 
> > 
> > I really don't want to have to do this in code. 
> > 
> > Is there a 'secret' way to do this in the/an/some ini file
> Not specifically, as far as I can tell. 
> 
> First you need to define what you mean by "session timeout". It could 
> easily mean one of two things: 
> 
> 1. The maximum duration of a session. So a session would be destroyed 
> a specified time after it was first created, even if it was in use. 
> 
> 2. The length of time after a session's last use that it will be discarded. 
> So a session would continue to exist as long as it was used again within 
> the timeout period, but would be destroyed if not used again within the 
> timeout. 
> 
> There doesn't appear to be a php.ini setting specifically for either scenario. 
> There are some statistical garbage collection settings for cleaning up old 
> sessions when using a global file-based session store. But they are basically 
> resource management rather than hard lifetime enforcement. 
> 
> Cheers 
> Tony 
> -- 
> Tony Mountifield 
> Work: to...@softins.co.uk - http://www.softins.co.uk 
> Play: to...@mountifield.org - http://tony.mountifield.org

[toc] | [prev] | [next] | [standalone]

#19400

In article <f5e01cbf-1fcb-4675-82eb-c328cf0f64c9n@googlegroups.com>,
K  <yyyyyeeeee00000@writeme.com> wrote:
>Get to watch Jesus videos !
>
>youtu.be/-3nN9-C1yKU
>
>...
>......
>...........
>.........................
>.......................................
>...................................................
>.....................................................................
>...........................................................................=
>..................
>
>
>
>
>On Wednesday, May 16, 2018 at 3:11:23=E2=80=AFPM UTC+2, Tony Mountifield wr=
>ote:
>> In article <pdh718$u78$1...@dont-email.me>,
>> madwomans Dad <dsvir...@gmail.com> wrote:=20
>> > I'm trying to find out if it's possible to configure session timeout in=
>=20
>> > some ini file=20
>> >=20
>> > $ php -version=20
>> > PHP 7.1.14 (cli) ...=20
>> >=20
>> >=20
>> > $ cat ./opt/alt/php71/etc/php.ini | grep session=20
>> >=20
>> > I can see all sorts of stuff but what I want is something in the ini=20
>> > file like session.timeout=3Dwhatever=20
>> >=20
>> > I really don't want to have to do this in code.=20
>> >=20
>> > Is there a 'secret' way to do this in the/an/some ini file
>> Not specifically, as far as I can tell.=20
>>=20
>> First you need to define what you mean by "session timeout". It could=20
>> easily mean one of two things:=20
>>=20
>> 1. The maximum duration of a session. So a session would be destroyed=20
>> a specified time after it was first created, even if it was in use.=20
>>=20
>> 2. The length of time after a session's last use that it will be discarde=
>d.=20
>> So a session would continue to exist as long as it was used again within=
>=20
>> the timeout period, but would be destroyed if not used again within the=
>=20
>> timeout.=20
>>=20
>> There doesn't appear to be a php.ini setting specifically for either scen=
>ario.=20
>> There are some statistical garbage collection settings for cleaning up ol=
>d=20
>> sessions when using a global file-based session store. But they are basic=
>ally=20
>> resource management rather than hard lifetime enforcement.=20
>>=20
>> Cheers=20
>> Tony=20
>> --=20
>> Tony Mountifield=20
>> Work: to...@softins.co.uk - http://www.softins.co.uk=20
>> Play: to...@mountifield.org - http://tony.mountifield.org

This abusive spamtroll came from

comp.lang.php #167987 (1 more)
X-Received: by 2002:ac8:5616:0:b0:3c0:326:efb3 with SMTP id 22-
+           20020ac85616000000b003c00326efb3mr7487583qtr.2.1678550011402;
+           Sat, 11 Mar 2023 07:53:31 -0800 (PST)
X-Received: by 2002:a81:ae66:0:b0:541:7266:3fd7 with SMTP id
+           g38-20020a81ae66000000b0054172663fd7mr841171ywk.3.1678550010941;
+           Sat, 11 Mar
+           2023 07:53:30 -0800 (PST)
Path: news.nk.ca!news.uzoreto.com!peer01.ams4!peer.am4.highwinds-media.com!
+     peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-
+     out.google.com!nntp.google.com!postnews.google.com!google-groups.
+     googlegroups.com!not-for-mail
Newsgroups: comp.lang.php
Date: Sat, 11 Mar 2023 07:53:30 -0800 (PST)
In-Reply-To: <pdhal4$s6m$1@softins.softins.co.uk>
Injection-Info: google-groups.googlegroups.com; posting-host=85.253.192.41;
+               posting-account=HfIszAoAAAC8ch6q3uChpTWUALHCfEoF
NNTP-Posting-Host: 85.253.192.41
References: <pdh718$u78$1@dont-email.me> <pdhal4$s6m$1@softins.softins.co.uk>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f5e01cbf-1fcb-4675-82eb-c328cf0f64c9n@googlegroups.com>
Subject: Re: php ini
From: K <yyyyyeeeee00000@writeme.com>
Injection-Date: Sat, 11 Mar 2023 15:53:31 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3384
Xref: news.nk.ca comp.lang.php:167987


Spamtrollers are trolls posting useless spam thinking it is content
but are posting useless noise. Spamtrolls are newsgroup vandals!
Thoses trolls are as bad as Donald 
Trump on Twitter.

This makes
https://groups.google.com/search/conversations?q=Depeer%20Google%20Groups

Depeer Google groups Now!!
-- 
Member - Liberal International This is doctor@nk.ca Ici doctor@nk.ca
Yahweh, King & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b 
Over-management takes all the fun out of life, as does nothing but fun. -unknown Beware https://mindspring.com

[toc] | [prev] | [next] | [standalone]

#17737

madwomans Dad wrote:

> I'm trying to find out if it's possible to configure session timeout in
> some ini file
> 
> $ php -version
> PHP 7.1.14 (cli) ...
> 
> 
> $ cat  ./opt/alt/php71/etc/php.ini | grep session
> 
> I can see all sorts of stuff but what I want is something in the ini
> file like session.timeout=whatever

You are looking for the "session.cookie_lifetime" setting in php.ini
If that setting is not explicitly set, then it defaults to "0", meaning that 
the session cookie will last "until the browser is closed". OTOH, if the 
setting /is/ set in php.ini, the value specifies the lifetime of the session 
cookie in seconds.

See
  http://php.net/manual/en/session.configuration.php

[snip]

FWIW, this is a global php setting; if you have multiple pages, each with 
their own session criteria, you can override this default by passing the 
appropriate value in the session_start() call.

-- 
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request

[toc] | [prev] | [next] | [standalone]

#17739

Lew Pitcher wrote:

> You are looking for the "session.cookie_lifetime" setting in php.ini

Not necessarily.

> […]
>   http://php.net/manual/en/session.configuration.php
> 
> [snip]
> 
> FWIW, this is a global php setting;

It does not have to.

> if you have multiple pages,

You mean Web _sites_.

> each with their own session criteria, you can override this default by
> passing the appropriate value in the session_start() call.

(They said that they do not want to do it in code.)

Provide an additional configuration (file) for each site instead.
 
-- 
PointedEars
Zend Certified PHP Engineer <http://www.zend.com/en/yellow-pages/ZEND024953>
<https://github.com/PointedEars> | <http://PointedEars.de/wsvn>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#17740

Thomas 'PointedEars' Lahn wrote:

> Lew Pitcher wrote:
> 
>> You are looking for the "session.cookie_lifetime" setting in php.ini
> 
> Not necessarily.
> 
>> […]
>>   http://php.net/manual/en/session.configuration.php
>> 
>> [snip]
>> 
>> FWIW, this is a global php setting;
> 
> It does not have to.

Yes, it does.

You can /override/ the setting, but that takes a deliberate act.

>> if you have multiple pages,
> 
> You mean Web _sites_.

No, I mean multiple pages.

>> each with their own session criteria, you can override this default by
>> passing the appropriate value in the session_start() call.
> 
> (They said that they do not want to do it in code.)

Yes, so? My answer stands: use the "session.cookie_lifetime" setting in 
php.ini

> Provide an additional configuration (file) for each site instead.

What sort of "configuration (file)"? And, how do /you/ control separate 
sessions per page (yes, you /can/ do that)?

-- 
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request

[toc] | [prev] | [next] | [standalone]

#17743

Lew Pitcher wrote:

> Thomas 'PointedEars' Lahn wrote:
>> Lew Pitcher wrote:
>>> You are looking for the "session.cookie_lifetime" setting in php.ini
>> 
>> Not necessarily.

Because that setting is not the only one that controls the availability of 
session information.

>>> […]
>>>   http://php.net/manual/en/session.configuration.php
>>> 
>>> [snip]
>>> 
>>> FWIW, this is a global php setting;
>> 
>> It does not have to.
> 
> Yes, it does.
> 
> You can /override/ the setting, but that takes a deliberate act.

I would assume that depends on how the PHP executable is compiled.
 
>>> if you have multiple pages,
>> You mean Web _sites_.
> 
> No, I mean multiple pages.

First of all, *there* *are* *no* (*Web*) *pages*.  Get rid of that outdated 
concept NOW.

Second, it is a bad idea for different parts of the same Web site to have 
different session lifetimes, unless they are part of distinct applications 
that are presented as such to the user.

Even then, users usually expect a Web site, and in a broader context, a Web 
application as a service to other Web resources, to work consistently 
throughout.  If the session is the result of a login process, they will not 
appreciate that this session times out earlier in one section of the Web 
site or one feature of the Web service than in another.
 
>>> each with their own session criteria, you can override this default by
>>> passing the appropriate value in the session_start() call.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> (They said that they do not want to do it in code.)
> 
> Yes, so?

So this particular suggestion is the exact opposite of what the OP is 
looking for.  (Is that not blatantly obvious?)

One valid reason why one would not want to do it in code is that the code 
must not or is not supposed to be modified.

> My answer stands: use the "session.cookie_lifetime" setting in
> php.ini

If one does that, then that affects all parts of all sites hosted on the 
same (virtual) server.  Bad idea, and often not even possible as prevented 
by administrative locks.
 
>> Provide an additional configuration (file) for each site instead.
> 
> What sort of "configuration (file)"?

This setting and many other session-related settings have a changeable mode 
of PHP_INI_ALL, which means that they can be set in php.ini and in PHP 
source code, but also in httpd.conf (including the virtual host 
configuration), and per directory in a .htaccess or .user.ini file 
(therefore, “file” in parentheses).

> And, how do /you/ control separate sessions per page (yes, you /can/ do
> that)?

That depends on what *you* mean by “page”.  This term is underdefined at 
best.

For different dynamically generated Web documents, that belong to the same 
application, I would not do it.

For distinct applications, using different session.save_path, which also can 
be be set in one of the ways that I described above; preferably _not_ in 
php.ini or code.  In fact, different session directiories is the recommended 
approach, so that different sessions of different applications on the same 
server do not interfere, can expire, be garbage collected, and be reset 
manually if necessary, independently.

-- 
PointedEars
Zend Certified PHP Engineer <http://www.zend.com/en/yellow-pages/ZEND024953>
<https://github.com/PointedEars> | <http://PointedEars.de/wsvn>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#17744

On 5/16/2018 1:59 PM, the internet troll Thomas 'Pointed Head' Lahn wrote:
> Lew Pitcher wrote:
> 
>> Thomas 'PointedEars' Lahn wrote:
>>> Lew Pitcher wrote:
>>>> You are looking for the "session.cookie_lifetime" setting in php.ini
>>>
>>> Not necessarily.
> 
> Because that setting is not the only one that controls the availability of
> session information.
>

It is a global setting. It may be overridden, but that does not mean 
it's not a global setting.

>>>> […]
>>>>    http://php.net/manual/en/session.configuration.php
>>>>
>>>> [snip]
>>>>
>>>> FWIW, this is a global php setting;
>>>
>>> It does not have to.
>>
>> Yes, it does.
>>
>> You can /override/ the setting, but that takes a deliberate act.
> 
> I would assume that depends on how the PHP executable is compiled.
>   

Nope.  It has nothing to do with the way the PHP executable is compiled. 
  It is standard PHP.

>>>> if you have multiple pages,
>>> You mean Web _sites_.
>>
>> No, I mean multiple pages.
> 
> First of all, *there* *are* *no* (*Web*) *pages*.  Get rid of that outdated
> concept NOW.
> 

Wrong again.  The concept of web pages is still very valid.

> Second, it is a bad idea for different parts of the same Web site to have
> different session lifetimes, unless they are part of distinct applications
> that are presented as such to the user.
> 

There are also valid reasons for having different timeout values for 
different parts of a site.

> Even then, users usually expect a Web site, and in a broader context, a Web
> application as a service to other Web resources, to work consistently
> throughout.  If the session is the result of a login process, they will not
> appreciate that this session times out earlier in one section of the Web
> site or one feature of the Web service than in another.
>   

It all depends on the site.  And this is HIS site, not YOURS.  You code 
your site like you want.  Don't try to tell other people how to code 
their site - especially when your information is WRONG.

>>>> each with their own session criteria, you can override this default by
>>>> passing the appropriate value in the session_start() call.
>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>> (They said that they do not want to do it in code.)
>>
>> Yes, so?
> 
> So this particular suggestion is the exact opposite of what the OP is
> looking for.  (Is that not blatantly obvious?)
> 
> One valid reason why one would not want to do it in code is that the code
> must not or is not supposed to be modified.
> 

It gives another option.  Period.

>> My answer stands: use the "session.cookie_lifetime" setting in
>> php.ini
> 
> If one does that, then that affects all parts of all sites hosted on the
> same (virtual) server.  Bad idea, and often not even possible as prevented
> by administrative locks.
>   

That is true, and that is exactly how it works.  "Administrative locks" 
(whatever they are) have nothing to do with it.

>>> Provide an additional configuration (file) for each site instead.
>>
>> What sort of "configuration (file)"?
> 
> This setting and many other session-related settings have a changeable mode
> of PHP_INI_ALL, which means that they can be set in php.ini and in PHP
> source code, but also in httpd.conf (including the virtual host
> configuration), and per directory in a .htaccess or .user.ini file
> (therefore, “file” in parentheses).
> 

That does not change the fact the settings in the php.ini file are global.

>> And, how do /you/ control separate sessions per page (yes, you /can/ do
>> that)?
> 
> That depends on what *you* mean by “page”.  This term is underdefined at
> best.
> 

The term is well defined and has been for over 25 years.

> For different dynamically generated Web documents, that belong to the same
> application, I would not do it.
>

He's not you.

> For distinct applications, using different session.save_path, which also can
> be be set in one of the ways that I described above; preferably _not_ in
> php.ini or code.  In fact, different session directiories is the recommended
> approach, so that different sessions of different applications on the same
> server do not interfere, can expire, be garbage collected, and be reset
> manually if necessary, independently.
> 

Whatever.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

[toc] | [prev] | [next] | [standalone]

#17741

On 05/16/18 16:38, Lew Pitcher wrote:
> madwomans Dad wrote:
> 
>> I'm trying to find out if it's possible to configure session timeout in
>> some ini file
>>
>> $ php -version
>> PHP 7.1.14 (cli) ...
>>
>>
>> $ cat  ./opt/alt/php71/etc/php.ini | grep session
>>
>> I can see all sorts of stuff but what I want is something in the ini
>> file like session.timeout=whatever
> 
> You are looking for the "session.cookie_lifetime" setting in php.ini
> If that setting is not explicitly set, then it defaults to "0", meaning that 
> the session cookie will last "until the browser is closed". OTOH, if the 
> setting /is/ set in php.ini, the value specifies the lifetime of the session 
> cookie in seconds.
> 
> See
>   http://php.net/manual/en/session.configuration.php
> 
> [snip]
> 
> FWIW, this is a global php setting; if you have multiple pages, each with 
> their own session criteria, you can override this default by passing the 
> appropriate value in the session_start() call.

You can also configure it on a directory based level in a similar way as
in the php.ini.

-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#17738

madwomans Dad wrote:
^^^^^^^^^^^^^
This is not a chatroom. Get a real name.

> I'm trying to find out if it's possible to configure session timeout in
> some ini file
> 
> $ php -version
> PHP 7.1.14 (cli) ...
> 
> 
> $ cat  ./opt/alt/php71/etc/php.ini | grep session

(UUOC.  Use

  grep -e session ./opt/…

instead.)

Are you sure that this is the correct file?  Likely it is not.
Use

  php -i | grep -e '\.ini'

to find out, if you are actually using the CLI for the sessions.

Otherwise, read <http://php.net/phpinfo>.
 
> I can see all sorts of stuff but what I want is something in the ini
> file like session.timeout=whatever

Possible reasons why you cannot find it there:

1. Wrong php.ini
2. PHP uses additional .ini files in which it is set instead
3. PHP uses the default
 
> I really don't want to have to do this in code.

You do not have to.
 
> Is there a 'secret' way to do this in the/an/some ini file

Yes, RTFM.

-- 
PointedEars
Zend Certified PHP Engineer <http://www.zend.com/en/yellow-pages/ZEND024953>
<https://github.com/PointedEars> | <http://PointedEars.de/wsvn>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

[toc] | [prev] | [next] | [standalone]

#17742

On 05/16/18 16:48, Thomas 'PointedEars' Lahn wrote:
> madwomans Dad wrote:
> ^^^^^^^^^^^^^
> This is not a chatroom. Get a real name.
> 
>> I'm trying to find out if it's possible to configure session timeout in
>> some ini file
>>
>> $ php -version
>> PHP 7.1.14 (cli) ...
>>
>>
>> $ cat  ./opt/alt/php71/etc/php.ini | grep session
> 
> (UUOC.  Use
> 
>   grep -e session ./opt/…
> 
> instead.)

or

grep session ./opt/alt/php71/etc/php.ini

> Are you sure that this is the correct file?  Likely it is not.
> Use
> 
>   php -i | grep -e '\.ini'

or even better

php -i | grep -i loaded\ configuration\ file

but keep in mind that this will display the path to the ini file used by
the cli version of PHP which can be a completely different file from
what the web service uses.

-- 

 //Aho

[toc] | [prev] | [next] | [standalone]

#17745

On 16/05/2018 13:09, madwomans Dad wrote:
> I'm trying to find out if it's possible to configure session timeout in 
> some ini file
> 
> $ php -version
> PHP 7.1.14 (cli) ...
> 
> 
> $ cat  ./opt/alt/php71/etc/php.ini | grep session
> 
> I can see all sorts of stuff but what I want is something in the ini 
> file like session.timeout=whatever
> 
> I really don't want to have to do this in code.
> 
> Is there a 'secret' way to do this in the/an/some ini file
> 
> Thanks
> 
> madwomans Dad

Thanks to all for the advice.

Lots to think about

real name
madwomans Dad

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.php

csiph-web