Kolab startup script

[Felipe Mendel N. Prates]

I think I got it... the guilty is SElinux. after enabling -x on the
startup script and debug on pam_selinux.so, here is how the syslog
output looks like...

Nov 24 12:14:00 server kolab: + '[' '!' -f /kolab/etc/rc ']'
Nov 24 12:14:00 server kolab: ++ basename /etc/rc5.d/S99kolab
Nov 24 12:14:00 server kolab: + PRGNAME=S99kolab
Nov 24 12:14:00 server kolab: + case $PRGNAME in
Nov 24 12:14:00 server kolab: + mode=start
Nov 24 12:14:00 server kolab: + case $mode in
Nov 24 12:14:00 server kolab: + /kolab/etc/rc all start
Nov 24 12:14:01 server su: pam_selinux: Open Session
Nov 24 12:14:01 server su(pam_unix)[8161]: session opened for user
kolab-r by (uid=0)
Nov 24 12:14:01 server su[8161]: pam_selinux: Open Session
Nov 24 12:14:01 server su[8161]: pam_selinux: Your default context is
user_u:system_r:unconfined_t.
Nov 24 12:14:01 server su[8161]: pam_selinux: Do you want to choose a
different one? [n]

now the question is: can this be fixed without disabling selinux? I've
been using selinux since I installed Kolab and just after some weeks
this started happening... why?

thank you all,
Felipe


On 11/22/05, Bernhard Reiter <bernhard.reiter at intevation.de> wrote:
> Am Montag, 21. November 2005 13:52 schrieb Felipe Mendel N. Prates:
> > Well, you're right, with the 'exec' there, the echo output is not
> > displayed. But removing the 'exec' still doesn't solve my particular
> > problem. With or without the exec, the startup still hangs! :-(
>
> Strange.
> You could try to add "-x" to the bash scripts to get more information
> about where it is actually hanging.
>
> You could grep the the question asked to see if you find it in the source
> code. It could be in a function that got defined on your system somehow.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>