Hi all,
I have tested WebYaST with nginx - works great! (I have fixed some small issues -
patched lib64 path in nginx.conf was broken after update, also I have moved the
patching call to %build (from %post) so rpm -V doesn't complain just after package
installation...)
And I have fixed nginx build in OBS YaST:Web (I have fixed more problems,
now all packages in YaST:Web now build) and I have noticed that webyast-base-*
packages contain some nginx related files like
mime.types
koi-utf
koi-win
scgi_params
...
These files also part of nginx package (in /etc/nginx). What about symlinking them to
/etc/nginx so we don't have to update them when a new nginx is released? Or do we
really need to have separate copies of these files?
Schubi?
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Here some overview about the memory usage. The docu of nginx has said
that the important value is RSS.
=============== Nginx in "not used" mode ==================
---------- Nginx processes ----------
PID PPID VMSize Private Name
-------------------------------------
24617 1 14.4 MB 0.2 MB nginx: master process /usr/sbin/nginx -c
/etc/yastws/nginx.conf
24618 24617 14.6 MB 0.4 MB nginx: worker process
24665 1 14.4 MB 0.2 MB nginx: master process /usr/sbin/nginx -c
/etc/yastwc/nginx.conf
24666 24665 14.7 MB 0.6 MB nginx: worker process
### Processes: 4
### Total private dirty RSS: 1.36 MB
---- Passenger processes -----
PID VMSize Private Name
------------------------------
24601 3.9 MB 0.2 MB PassengerWatchdog
24603 13.3 MB 0.3 MB PassengerHelperAgent
24604 7.5 MB 4.6 MB Passenger spawn server
24607 7.9 MB 0.5 MB PassengerLoggingAgent
24649 3.9 MB 0.2 MB PassengerWatchdog
24651 13.3 MB 0.4 MB PassengerHelperAgent
24652 7.5 MB 4.6 MB Passenger spawn server
24655 7.9 MB 0.5 MB PassengerLoggingAgent
### Processes: 8
### Total private dirty RSS: 11.25 MB
=============== Nginx in "used" mode ==================
---------- Nginx processes ----------
PID PPID VMSize Private Name
-------------------------------------
24617 1 14.4 MB 0.2 MB nginx: master process /usr/sbin/nginx -c
/etc/yastws/nginx.conf
24618 24617 14.6 MB 0.4 MB nginx: worker process
24665 1 14.4 MB 0.2 MB nginx: master process /usr/sbin/nginx -c
/etc/yastwc/nginx.conf
24666 24665 14.7 MB 0.5 MB nginx: worker process
### Processes: 4
### Total private dirty RSS: 1.27 MB
---- Passenger processes -----
PID VMSize Private Name
------------------------------
24601 3.9 MB 0.2 MB PassengerWatchdog
24603 13.3 MB 0.3 MB PassengerHelperAgent
24604 7.5 MB 4.5 MB Passenger spawn server
24607 7.9 MB 0.5 MB PassengerLoggingAgent
24649 3.9 MB 0.2 MB PassengerWatchdog
24651 13.3 MB 0.4 MB PassengerHelperAgent
24652 7.5 MB 4.5 MB Passenger spawn server
24655 7.9 MB 0.5 MB PassengerLoggingAgent
24683 59.1 MB 36.7 MB Rails: /srv/www/yast
24689 60.4 MB 37.0 MB Rails: /srv/www/yastws
### Processes: 10
### Total private dirty RSS: 84.68 MB
=============== lighttpd everytime ==================
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
lighttpd 5848 0.0 0.5 6724 2704 ? S 15:05 0:00
/usr/sbin/lighttpd -f /srv/www/yast/config/lighttpd.conf
lighttpd 5853 0.9 7.7 58980 39436 ? S 15:05 0:09
/usr/bin/ruby /srv/www/yast/public/dispatch.fcgi
yastws 5875 0.0 0.2 6156 1416 ? S 15:05 0:00
/usr/sbin/lighttpd -f /etc/yastws/lighttpd.conf
yastws 5877 0.9 8.1 61380 41612 ? S 15:05 0:10
/usr/bin/ruby /srv/www/yastws/public/dispatch.fcgi
### Processes: 4
### Total private dirty RSS: 85,17 MB
Greetings
Stefan
P.S.: BTW: In the last workshop we have said that WebYaST consumes more
than 200 MByte.
Does anyone knows how this value has been evaluated ?
Am 06.12.2010 11:27, schrieb Stefan Schubert:
> Hi,
> as the master is open for changes now I would like to run WebYaST with
> nginx now. (As the benefits which I have described some time ago).
> Are there any objections to use nginx as default in the future ?
>
> Greetings
> Stefan
>
> Am 25.11.2010 10:15, schrieb Martin Vidner:
>
>> Hi,
>>
>> I have updated the branch page
>> http://en.opensuse.org/openSUSE:WebYaST_Branches
>> and created the maintenance branch for WY 1.1 (so that I could fix
>> the RPM dependencies for the SP1 update, which is still in
>> progress).
>>
>> So the master branch is now open to integrate your own branches.
>>
>>
>
--
*******************************************************************************
Stefan Schubert
SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany
e-mail: schubi(a)suse.de
-------------------------------------------------------------------------------
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-devel+help(a)opensuse.org
Hi,
I have updated the branch page
http://en.opensuse.org/openSUSE:WebYaST_Branches
and created the maintenance branch for WY 1.1 (so that I could fix
the RPM dependencies for the SP1 update, which is still in
progress).
So the master branch is now open to integrate your own branches.
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu