In our rc.stop & rc.start scripts the parts about stopping and starting the printerdaemon are excluded.

We stop and start our Baan system every week and reboot the server regularly. Luckely printing is not a problem; can anyone explain to me how this is possible?

regards

Max

We use c3 on HPUX and use the Unix printing services in stead of the Baan printerdaemon. In the program field of the devices we use something like: lp -c -dp15 -n%d -s %s. Where lp is the Unix print command.

Walter Grimm

Hi there,

The printer daemon in baan is used for two things:

a) If a printer is of type "Printer", then the printer daemon actually forms the unix command needed for printing. If the type if of type "direct", then the command is directly configured with the printer.

b) The printer daemon checks, whether temporary print files in $BSE_TMP exceed the "delete delay time" (configured in user management of baan) and delete files accordingly.

In a lot of installations the printer daemon is disabled, because it was buggy for a long time and took too many system ressources.

As long as you clean up your $BSE_TMP with other means, then you do not need the pdaemon at all.

Is it not nice, that a whole daemon might be down and Baan keeps on working?
Try to kill shmtimer6.1 and see what will happen ...


Regards

Markus

In our case, the printer daemon is necessary but the startup/shutdown scripts did not work properly. So I added this to rc.stop

# Stop the Printer Daemon
echo 'Stop Running pdaemon\n'
for i in `ps -ef|grep pdaemon|grep -v "grep pdaemon"|awk '{print $2}'`
do
kill -15 ${i}
done

but left rc.start as

# Initialize Printer Daemon
if [ ${licd_pdaemon} -eq 1 ];then
${BSE}/etc/rc.start_pdaemon
fi

and everything worked well after that. The reason I changed rc.start (and possibly the reason it not used at your site) is the original pdaemon stop script did not work and therefore rc.stop would not finish (# of attach eq 1).