re authorization is setup
and use xauth rather than xhost.
--
/* Dale Southard Jr. [EMAIL PROTECTED] 925-422-1463 fax 422-9429 */
/* Computer Scientist, Advanced Simulation and Computing Program */
/* L-073, Lawrence Livermore National Lab, Livermore CA 94551 */
--
To UNSUBS
or less correct.
If you can connect to an X11 server, you can use either the RECORD,
XTrap, or DEC-XTrap extensions to access the protocol stream. You can
also take control of input devices using XTEST. There are some limits
(eg, I think openGL/GLX stuff that goes through DRI won't get pos
please) that does? Failing that, i am
> willing to write my own tool, if necessary, and would appreciate
> any pointers to good reference material (raw drive access and
> how to work with the images created).
--
/* Dale Southard Jr. [EMAIL PROTECTED] 925-422-146
please) that does? Failing that, i am
> willing to write my own tool, if necessary, and would appreciate
> any pointers to good reference material (raw drive access and
> how to work with the images created).
--
/* Dale Southard Jr. [EMAIL PROTECTED] 925-422-146
SGID).
In cups, the print data is transferred to the server via http
protocol. This means the client program doesn't need any special
privileges, but does require that the server be listening on a port
somewhere.
Which is ultimately a better idea from a security perspective is a
matter of opini
SGID).
In cups, the print data is transferred to the server via http
protocol. This means the client program doesn't need any special
privileges, but does require that the server be listening on a port
somewhere.
Which is ultimately a better idea from a security perspective is a
matter of
of other hooks. The
manuals are avaiable at http://localhost:631/ or at cups.org.
> >
> > route add -net 224.0.0.0 netmask 240.0.0.0 dev
> >
> > What's up with that? I didn't see anything in the doc about that
> > either.
Google for the term ``multi
and lots of other hooks. The
manuals are avaiable at http://localhost:631/ or at cups.org.
> >
> > route add -net 224.0.0.0 netmask 240.0.0.0 dev
> >
> > What's up with that? I didn't see anything in the doc about that
> > either.
Google for the term ``multi
ng from in the shell script and
> the address is assigned dynamically.
echo $SSH_CLIENT | awk '{print $1}'
or
echo $SSH2_CLIENT | awk '{print $1}'
--
/* Dale Southard Jr. [EMAIL PROTECTED] 925-422-1463, fax 422-9429 */
/* Computer Scientist, Accelerated Strate
ng from in the shell script and
> the address is assigned dynamically.
echo $SSH_CLIENT | awk '{print $1}'
or
echo $SSH2_CLIENT | awk '{print $1}'
--
/* Dale Southard Jr. [EMAIL PROTECTED] 925-422-1463, fax 422-9429 */
/* Computer Scientist, Accelerated Strate
Marko Kreen writes:
> On Thu, Aug 09, 2001 at 12:38:52PM -0700, Dale Southard wrote:
> > Marko Kreen writes:
> > > Well, we have basically one init script per package. Now I want
> > > state, that _nothing_ from this package gets started. Do I need
> > >
hat is/isn't
started.
But in Debian there are still some individual options that require
editing of init.d scripts to enable or disable (see the mountnfs.sh
and networking scripts for examples). Whether or not this makes
adding a system like chkconfig ``worth the trouble'' is another
q
Marko Kreen writes:
> On Wed, Aug 08, 2001 at 02:56:46PM -0700, Mike Fedyk wrote:
> > On Wed, Aug 08, 2001 at 08:44:50PM +0200, Marko Kreen wrote:
> > > On Wed, Jul 25, 2001 at 11:05:25AM -0700, Dale Southard wrote:
> > > > Why not use something like the IRIX `
't change the on|off status of the
service in the config directory. Of course it also means putting the
above bit of logic in every init.d script that is put under chkconfig
control and adding the necessary logic to the postinst script to
create the config entry if it doesn't exist yet...
rvice in the config directory. Of course it also means putting the
above bit of logic in every init.d script that is put under chkconfig
control and adding the necessary logic to the postinst script to
create the config entry if it doesn't exist yet...
--
/* Dale Southard Jr. [EMA
her or
not it would be a useful addition to Debian is another question
Joseph Pingenot <[EMAIL PROTECTED]> writes:
> From Dale Southard on Tuesday, 19 June, 2001:
> Hrm. That could be rather easy to implement. The guaranteed
> way to see if something's going to be started
s easier for newbie
admins than the Red Hat chkconfig implementation or symlink
creation/deletion). It's fairly simple to turn things on/off, and
there are few surprises during updates.
--
/* Dale Southard Jr. [EMAIL PROTECTED]925-422-1463 */
/* Computer Scientist, Accelerate
her or
not it would be a useful addition to Debian is another question
Joseph Pingenot <[EMAIL PROTECTED]> writes:
> From Dale Southard on Tuesday, 19 June, 2001:
> Hrm. That could be rather easy to implement. The guaranteed
> way to see if something's going to be started
s easier for newbie
admins than the Red Hat chkconfig implementation or symlink
creation/deletion). It's fairly simple to turn things on/off, and
there are few surprises during updates.
--
/* Dale Southard Jr. [EMAIL PROTECTED]925-422-1463 */
/* Computer Scientist, Accelerate
19 matches
Mail list logo
