+++ linuxlingam [17/09/03 16:21 +0530]:
> 1) typed $which firestarter
> and to this one, did a chmod u+s, as well as a g+s, to set sticky bits.
> 
> for good measure, did the chmod U+s and g+s to the firestarter in /usr/bin,
> to the one in /usr/sbin, to also the /usr/bin/consolehelper that i found
> /usr/bin/firestarter was pointing to.
> 
> finally, did a ls -l check on all these to confirm the sticky bit.

Eeep. Avoid the SUID bits will you? Some security programs check whether they
are running under setuid mode(real and effective users being different) and
to prevent breaches refuse to work.

Instead use sudo to start firestarter as root. No problems there. (Haven't
used firestarter though).
> 
> tried launching firestarter. the prompt for the root password did not come,
> but firestarter did not launch either.

Try running from an xterm and note if any messages come out. If none, try
running under strace and look at the last 10-15 lines to catch any pattern
(using tail). You might make out some checks that the program is doing before
exiting.

> earlier, had also made an entry in /etc/rc.local for the command to
> automatically launch firestarter at boot time. is the above problem the
> reason it did not launch, either?

No clue. Should have run.

- Sandip

-- 
Sandip Bhattacharya                        http://www.sandipb.net
sandip at puroga.com
Puroga Technologies Pvt. Ltd. 
http://www.puroga.com

_______________________________________________
ilugd mailing list
[EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd

Reply via email to